Selfhosted

39435 readers

4 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

How to organize docker volumes into subdirectories using compose (feddit.de)

submitted 1 year ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

Hei there. I've read that it's best practice to use docker volumes to store persistent container data (such as config, files) instead of using bindmount. So far, I've only used the latter and would like to change this.

From what I've read, all volumes are stored in var/lib/docker/volumes. I also understood, that a volume is basically a subdirectory in that path.

I'd like to keep things organized and would like the volumes of my containers to be stored in subdirectories for each stack in docker compose, e.g.

volumes/arr/qbit /arr/gluetun /nextcloud/nextcloud /nextcloud/database

Is this possible using compose?

Another noob question: is there any disadvantage to using the default network docker creates for each stack/container?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 1 year ago (1 children)

Never heard that bindmounts are bad practice. Never had problems with it. What did you read?

If it ain't broken ...

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Yeah, that seems to be the gist of it. I've seen several people say that they prefer volumes as they are managed by docker and therefore easier to migrate / backup. Since I plan on moving to different hardware in the near future, I figured why not.

Also something about permissions, though I never had any problems with it. So as you said, I'm sticking with bind mounts for now.

Also I don't have a clue what I'm doing at least 50 percent of the time and just follow guides. That's why I wanted some clarification on that :)