Support for bind mounts #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I use bind mounts on all of my containers, but repliqate seems that not support it, so opened this Issue to request a support for bind mounts also.
This may already be possible, but I am still testing it. Looked safe with my first container,
gotify. I already had created the volumes manually before I dove into understanding automatic volume creation by docker (or podman).The following configuration mounted my existing directory within the container. Adding the necessary labels to backup the volume with
repliqateshould be trivial. I haven't finished setting up to test actual backups and restores yet.I have confirmed that backups are created with this setup. I have not confirmed restoration from these backups yet.
This is what I get when I setup repiqate to backup one of my containers:
I would REALLY love to see repliqate backup binds. Personally I'd have to rejig close to 200 Ansible roles to make repliqate work with my containers which is no small feat.
Could be my ignorance, but I only see about 10% (if that) of the docker-compose scripts that I run across binding via docker volumes. I bind everything to directly accessible local persistent storage. I thought this was common. Binding to volumes only came to the forefront of my attention when bumping into repliqate.
I appear to be an edge case here, but I don't feel that way...
@WiggleWizard - could you please post your thoughts on this issue?
Only reason repliqate doesn't have bind mount support right now is because I personally use volumes as it's easier for my own stack. However I do see a lot of people using bind mounts so support for it needs to be added, for sure.
It would probably take a few days to add but I'm currently in the middle of figuring out some IPC shinanigans with repliqate. Once that's done I'll get work done on bind mount support.
Only issue with bind mounts is setting them up with repliqate would be a little bit of a pain; you'd have to explicitly expose backup endpoints for each bind mount on repliqate, which kinda goes against the whole "automation" aspect of repliqate on a smaller scale. I've got some creative ideas to alleviate that sort of leg work though.
If you don't mind, would you be able to post a few examples of your setups? I'd like to understand your use case more, as I don't personally use bind mounts, so it's a little difficult for me to visualize.
This is great news. Thank you for taking my request seriously.
I posted an example in https://github.com/lminlone/repliqate/issues/23#issuecomment-3632229854 but here's another. It might look daunting at first, but I think it's very readable.