Submitted 1 day ago by enchantedgoldapple@sopuli.xyz to selfhosted@lemmy.world
For user-readable files or media I store them under ~/docker/data, and for everything else I store them under ~/docker/stacks/[service] where ~/docker/stacks is maintained by Dockge.
Is there a better way to do this?
I tend to use /opt/[service]/, like for example /opt/forgejo/. It’s outside of any user’s Homedir and it seems to fit into what the FHS 3.0 (Filesystem Hierarchy Standard) defines.
I use /srv/[service] for services by the same logic, and leave /opt for local user apps. It’s kind of a coin toss though. On another day I night have decided differently.
I do this as well. Though if I’m deploying a stack(grafana+prometheus+cadvisor) then it all goes under a single folder like /opt/stackname/
But if I’m running multiple services that are mostly separate or not in the same stack then they go in their own folders like /opt/nginx/ and /opt/grafana/
Yes, that’s what I meant, thanks for the clarification.
I have multiple compose stacks with one folder each, and they also contain all the bind volumes and any other extra files needed.
it makes it all so easy to scp that bitch!
Bind mounts aren’t specific to Docker. You’re asking specifically about bind mounts as used by Docker?
Yes
My docker mounts just point to the folder they live in.
I’d rather have the data stored next to the config so it’s easy to find and manage.
I mount them directly from the NAS inside docker volumes.
if there are any configuration/local data files that need to be persistent, those are usually kept in ~/project/{container}. the compose file is kept at the root project directory.
home user is a daemon user created specifically for running docker containers that does not have root privileges.
along with the compose.yaml file, unless I need it in a different drive for any reason
This is me.
For example, /srv/docker/synching contains:
compose.yml
.env
./Sync
That last one is a directory bound to the container which contains all my sync folders.
Occasionally it makes more sense to put the mounted folder in /srv like /srv/photos is mounted by /srv/docker/photoprism/compose.yml
However, thats a rarity. Things mostly accessed by a single compose stack are kept alongside the other files for that stack.
I always use /docker, but I recognize that’s probably not the most “correct” place.
Same here, separate disk mounted at /docker
I run a swarm and the NAS~esque machine has its exportfs entries under /export so all my docker persistence data goes into /export/docks/<stackname>/<service>/<mount>
/opt/docker/[service]
/docker/compose/<project> for compose and env files
/docker/data/<project> for data to be retained
I let the docker overlay handle all the volatile data.
I didn’t think much of what the “correct” location would be. But i have a general kinda everything share at /var/share/[music,books,video,user folders,repo]. And then any caching or config data sits in that dockers home folder under /etc/docker/[jellyfin,immich,kavita,etc] together with its docker-compose file. All docker services run under the group user so they all have access to the share.
Xdg. Its the only attempted standard for where to put things. Persistent data in ~/.config/docker/service. Others in similar directories under ~/.local/share, ~/.cache, etx.
I use the same naming convention as you for stacks, but since I’m running a docker swarm I have to mount the NFS in the exact same way on all my nodes, which are just 3 R-Pi 4s. It’s a little janky in that if the NFS goes offline all my services go along with it. Traefik works really well with a swarm, especially when you have it set to auto pick up any services and proxy them.
thisisnotausername@lemmy.dbzer0.com 5 hours ago
/srv/[stack name]/volumes/[binds]
I just like so much /srv is the best folder