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?

all 20 comments

sorted by: hot top controversial new old
[–] 20 points 10 months ago (3 children)

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.

  • source
  • hideshow 3 child comments
  • [–] 2 points 10 months ago (1 child)

    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/

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 10 months ago* (last edited 10 months ago)

    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.

    So a folder would be services and have a compose file, config folder, and a data folder with subdirectories per service I run. Any custom dockerfiles get a folder with their build scripts.

  • source
  • [–] 6 points 10 months ago (1 child)

    Bind mounts aren't specific to Docker. You're asking specifically about bind mounts as used by Docker?

  • source
  • hideshow 1 child comment
  • [–] 7 points 10 months ago (1 child)

    I always use /docker, but I recognize that's probably not the most "correct" place.

  • source
  • hideshow 1 child comment
  • [–] 4 points 10 months ago (1 child)

    along with the compose.yaml file, unless I need it in a different drive for any reason

  • source
  • hideshow 1 child comment
  • [–] 2 points 10 months ago

    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.

  • source
  • parent
  • /srv/[stack name]/volumes/[binds]

    I just like so much /srv is the best folder

  • source
  • [–] 2 points 10 months ago

    /opt/docker/[service]

  • source
  • [–] 2 points 10 months ago

    /docker/compose/ for compose and env files

    /docker/data/ for data to be retained

    I let the docker overlay handle all the volatile data.

  • source
  • [–] 1 point 10 months ago

    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.

  • source
  • [–] 1 point 10 months ago

    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.

  • source
  • [–] 1 point 10 months ago

    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///

  • source
  • [–] -1 points 10 months ago

    If you using bind mounts - you are using dockers in wrong way. Use named volumes.

  • source
  • [–] 0 points 10 months ago

    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.

  • source
  • [–] 0 points 10 months ago

    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.

  • source