this post was submitted on 20 Apr 2024
119 points (95.4% liked)

Selfhosted

40296 readers
220 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ShortN0te@lemmy.ml 52 points 7 months ago (3 children)

Who the hell is pulling the docker-compise.yml automatically every release? I find myself already crazy by pulling the latest release but the compose file is just a disaster waiting to happen.

[–] Bakkoda@sh.itjust.works 25 points 7 months ago

I honestly never once thought to do this. Ever. No likey.

[–] barbara@lemmy.ml 11 points 7 months ago* (last edited 7 months ago)

Especially since the original doesn't care about selinux and it would overwrite everything.

And it doesn't specify a repository which breaks auto updates of podman

[–] Lem453@lemmy.ca 5 points 7 months ago (2 children)

Complete insanity.

Then again it seems like people were using a docker volume to save all their precious photos rather than a mount point on the host. Also seems insane to me.

[–] ArcticDagger@feddit.dk 5 points 7 months ago* (last edited 7 months ago) (1 children)

Could you explain a bit more about why it's insane to have it as a docked volume instead of a mount point on the host? I'm not too well-versed with docker (or maybe hosting in general)

Edit: typo

[–] Lem453@lemmy.ca 2 points 7 months ago (1 children)

A normal file system is something anything can access. You can open it in file browser. You can get to it via command line. You can ssh into from another computer and you can easily back it up with numerous tried and tested backup methods.

Why lock yourself into only being able to access your data via docker?

In a disaster scenario when you are trying to recover files, you will greatly appreciate being able to just see all the files super easily without anything fancy. It also means you can use any standard method to back up all those file.

Recovery is also almost as easy, copy the files back to where they were and just run the docker container.

[–] ArcticDagger@feddit.dk 2 points 7 months ago

Thank you, those are some good points!

[–] jvh@feddit.uk 2 points 7 months ago (1 children)

What's the difference? The docker volume, on my setup anyway, is in /mnt/md0/docker-data/immich_upload/_data/

It's still a directory on the host either way? Although I guess if it's a mount point it won't get removed when removing volumes in docker.

[–] Lem453@lemmy.ca 2 points 7 months ago

That last point is the important one. For important data, I want the setup to be as easily accessible and system agnostic as possible.