Backup by volumes, not containers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 180
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Wouldn't it be nice to allow specifying what to backup on a volume level, not on a container one? Some volumes are shared between containers, and keeping track of where to backup which volume consumes mental capacity :)
I'd like to be able to configure my backups like this:
services:
postgres:
image: postgres:11
labels:
stack-back.postgres: true
volumes:
- pgdata:/var/lib/postgresql/data
...
volumes:
pgdata:
shared-state:
labels:
stack-back.backup: true
my-files:
# instead of bind mount, to specify labels
labels:
stack-back.backup: true
driver_opts:
type: none
o: bind
device: /srv/data
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing how stack-back currently discovers container labels and mounted volumes, then determine how Compose volume labels should select backup targets, including shared volumes and the bind-backed volume example. Done means volume-level configuration works without requiring container-level backup labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100