-
-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup/Restore workflow #25
Comments
You're looking at it. It's very common to store configuration files with There's GitHub or GitLab or BitBucket to name a few, or you can roll your own git server; though not recommended as all of the mentioned services allow for private repositories to house your configs. |
I am not so sure that you can keep these folders in git. In my 16-18 hours of usage of a docker-compose very similar to what is defined in the sample traefik2 displayed here, the /docker folder is close to 520 MB of data, already! I'm sure that some of the files are binary files too (images and thumbnails etc) These are NOT good candidates for a git repo. I was hoping something along the lines of a borg backup or similar, and I was wondering if someone had testdriven any dockerized solutions, like the other suite of applications shown in the repo. Thanks, but stuffing all that in the git repo, is not what I would consider proper backup strategy. |
Could debate with you that git can do binary files, images, and there are heaps of git repos that are much larger than you 520MB, but looks like you don't want that. Sure , use Borg or Rsync. Both can do incremental backups and restores. |
I can consider adding a backup system. But your comment on docker binaries etc is easily addressed with .gitignore. My .gitignore by default ignores all the contents of the folder and I explicitly specify which files I want to be published in my git repo. But the downside is you have to make sure you specify all important files. |
Sure, yes, I also intended to share my backup solution when I get around implementing it (along with some other optimizations I have in mind) The way I see it, is that all docker-compose and other config files are saved and source controlled in a git repo (pretty much as this repo is setup) but everything under Of course you have the issue of not being completely able to backup a set of running docker instances, but you could just Also the [Edit]: I just saw that you have reversed the usage of Thanks... |
The proposed setup put everything in the same "top level" folder:
In my own environment, I set it up as 2 folders:
|
I've just set up Duplicati service. It backs up folders to a myriad of cloud service. I've used this image: https://github.com/linuxserver/docker-duplicati |
Sorry, this is not really an "issue" per say, but rather a request.
What would be your suggestion for backing up/restoring this server...?
Not as much as the potential media files (that might add up to some TBs, and they ought to be residing to separate partitions or NASes anyways) but the
~/docker
folder that contains ALL the individual app settings and configurations.The text was updated successfully, but these errors were encountered: