Selfhosted

40201 readers

914 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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

How to access all files in docker volumes for backups? (feddit.de)

submitted 11 months ago* (last edited 11 months ago) by gitamar@feddit.de to c/selfhosted@lemmy.world

4 comments fedilink hide all child comments

I am using restic for backups. I would like to use a non-root user to backup my docker volumes. As the files in the volumes have very different access rights and groups, accessing them is difficult without root rights.

Chowning the files doesn't help sustainably, as new files are created with a different group again.

What recommendation do you have to smoothly backup files from the docker volumes?

Tags #restic #backup #docker

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

[–] bellsDoSing@lemm.ee 0 points 11 months ago (1 children)

You didn't mention how big those volumes are and how frequently the data changes.

Assuming it's not that much data:

use tar to archive each volume first, while using proper options to preserve permissions and whatever else is important for your usecase
use restic to backup those archives
use a proper pruning strategy to not let your backups get too big:
- I'm not that familiar with restic, but maybe you can backup those archives separately and apply a more aggressive pruning strategy just for them
- simply might be needed, cause deduplication (AFAIK) might not be that great with backing up archives
- but maybe if the volume data and the resulting archive doesn't change that often, deduplication would be sufficient even with a not so aggressive pruning strategy

[–] gitamar@feddit.de 1 points 11 months ago

Restic uses smart Delta backups, creating a tar before the restic process would defeat the purpose. The permission issue is the same, as I need to have access to the Files either way.