this post was submitted on 24 Mar 2025
29 points (96.8% liked)

Selfhosted

44984 readers
428 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
29
Does it ever make sense/is it possible to move certain docker volumes to another physical volume, but not all? (lemmy.world)
submitted 1 day ago by ch00f@lemmy.world to c/selfhosted@lemmy.world
18 comments fedilink hide all child comments
 

I'm hosting a few services using docker. For something like an openstreetmap tileserver, I'd like it to remain on my SSD because high speed improves performance, and the directory is unlikely to grow and fill the drive.

For other services like NextCloud, speed isn't as important as storage size, so I might want it on a larger HDD raid.

I know it's trivial to move the volumes directory to wherever, but can I move some volumes to one directory and some volumes to another?

you are viewing a single comment's thread
view the rest of the comments
[–] Dave@lemmy.nz 19 points 1 day ago (7 children)

I don't know if this is naughty but I use bind mounts for everything, and docker compose to keep it all together.

You can map directories or even individual files to directories/files on the host computer.

Normally I make a directory for the service then map all volumes inside a ./data directory or something like that. But you could easily bind to different directories. For example for photoprism I mount my photos from a data drive for it to access, mount the main data/database to a directory that gets backed up, and mount the cache to a directory that doesn't get backed up.

[–] suicidaleggroll@lemm.ee 15 points 1 day ago* (last edited 1 day ago) (1 children)

Same, I don't let Docker manage volumes for anything. If I need it to be persistent I bind mount it to a subdirectory of the container itself. It makes backups so much easier as well since you can just stop all containers, backup everything in ~/docker or wherever you put all of your compose files and volumes, and then restart them all.

It also means you can go hog wild with docker system prune -af --volumes and there's no risk of losing any of your data.

[–] Dave@lemmy.nz 4 points 1 day ago

Yes that's what I do too!

Overnight cron to stop containers, run borgmatic, then start the containers again.

load more comments (5 replies)