Selfhosted

40466 readers

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

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

Options in backing up persistent docker volumes? (self.selfhosted)

submitted 1 year ago by r0ckr to c/selfhosted

18 comments fedilink hide all child comments

Hi all

I'm running several docker containers with local persistent volumes that I would like to backup. I haven't found an easy method to do so.

What do you use / recommend to do that? AFAIK you can't just rsync the volume directory while the container is running.

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

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

Exactly the reason why i always exchange the volumes in any compose file with bind mounts.

Also you don‘t have the provlem of many dangling volumes

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

I don't even understand what the advantage is to using volumes rather than mounts? So I too always use mounts.

[–] [email protected] 2 points 1 year ago

I think volumes are useful when you don't want to deal with those files on the host. Mainly for development environments.

I wasn't able to understand volumes at first, and my team mate told me I had to use binders to run mysql. My project folder used to have a docker/mysql/data. Now I just point MySQL data to a volume so I don't loose data between restarts. And I don't have to deal with a mysql folder on my project with files I would never touch directly.

In my opinion, volumes are useful for development / testing environments.

[–] retrodaredevil 1 points 1 year ago

I'm not sure either. The only thing I could come up with is that with volumes you don't have to worry about file ownership. That's usually taken care of for you with volumes from what I understand.