This is way too hard for the casual docker user. This is only for experts and deep Linux nerds. I wish someone would make a docker backup docker where most would be configured through a web portal. It would me accessible for the masses.
Yes I can imagine. But you have to think that docker was actually developed for non-persistent containers or data.... So volumes do the exact opposite :-) But therefore tools were created to deal with these 'consequences'. Maybe have a look at portainer, which offers a nice web-ui for configuring docker container stacks. But still, it does not have a nice gui for volume backups. Maybe have a look at borgbackup and borgweb. (I haven't used them) it seems to offer a webui to use to configure stuff.
Can you give me some examples how to backup volumes that are managed in another docker-compose file? (And maybee how to create a weekly-backup AND a monthly-backup within the same configuration) Thanks a lot
Yes! Thanks for the hint! I just forgot to show that in the video, but having it planned for a future video as a catch up! And for the pgp, this was just to demonstrate how easy that works. But for sure, you should have it stored somewhere securely and then make sure it is not stored in plaintext in your git. But that's also a whole other discussion about credentials from a security perspective... millions of possibilities what to do and what not to do.. 😄
5:31 i wonder you ready only mount the docker socket. Can it then even interact with the containers? 11:44 and I hope that values are not valid anymore when the video goes online 😅 My backup strategy is still in concept state. Currently I redundant store my important data on all servers for redundancy for a hardware failure. But that sounds nice ❤ Edit: And I use resilio sync containers for that
You can try :-) But I made sure to disable this account 😜 The read only mode is just enough to interact with the docker socket. You are then just not able to modify the socket file itself
@@techwithmarco I have to admit: I’m pretty new to docker, but for example, watchtower needs access to the socket to affect the other containers. How does this work in this case with a read only mode? 🤔
@@TheOnlyEpsilonAlpha I think a might be wrong about the docker socket. I just got a comment under my traefik video, that there are other ways to use to docker sockert. Just google for docker-socket-proxy and there is a nice project on github which restrict access to the docker api. I'll take a look at it and maybe do another video about it.
Here is a tutorial on how to restore the backups with some easy steps to follow :)
czcams.com/video/FPiS6Cck4l0/video.html
Please don't give up and continue because you deserve 1m+
Yeah! That's the spirit. I already have 3 videos in the pipeline, but still to find time to edit them :-) So stay tuned!
Amazing explanation on how to work with docker-volume-backup. Thanks for this video. Subscribed!
Thanks a lot! Means a lot to me :-)
I am sorry for the shit focus on the camera after a while....
And by the way, if you have not subscribed yet, now it is the time! 😜😋
Very helpful tutorial, thanks a lot! :)
Amazing ! Waiting for Restore video 😉
Thanks! Good call! I have the video on my bucket list :-)
still waiting :-D @@techwithmarco
I hope the wait was worth it 😄
czcams.com/video/FPiS6Cck4l0/video.html
Your videos are very good
Thanks!
this is great! would love to see how to restore from these backups when something indeed goes wrong
Yes, it's already on my list to showcase that in one of my next videos :-)
+1
Here you go guys :)
czcams.com/video/FPiS6Cck4l0/video.html
This is way too hard for the casual docker user. This is only for experts and deep Linux nerds.
I wish someone would make a docker backup docker where most would be configured through a web portal. It would me accessible for the masses.
Yes I can imagine. But you have to think that docker was actually developed for non-persistent containers or data.... So volumes do the exact opposite :-) But therefore tools were created to deal with these 'consequences'.
Maybe have a look at portainer, which offers a nice web-ui for configuring docker container stacks. But still, it does not have a nice gui for volume backups.
Maybe have a look at borgbackup and borgweb. (I haven't used them) it seems to offer a webui to use to configure stuff.
Can you give me some examples how to backup volumes that are managed in another docker-compose file? (And maybee how to create a weekly-backup AND a monthly-backup within the same configuration) Thanks a lot
Remember to test restore. And a strategy for the pgp encryption pass.
Yes! Thanks for the hint! I just forgot to show that in the video, but having it planned for a future video as a catch up!
And for the pgp, this was just to demonstrate how easy that works. But for sure, you should have it stored somewhere securely and then make sure it is not stored in plaintext in your git.
But that's also a whole other discussion about credentials from a security perspective... millions of possibilities what to do and what not to do.. 😄
@@techwithmarcowhere are you from
Hi Marco, nice method, but I personaly prefere a proxmox server so I can easyly backup the complete docker-host regularly and automatically.
Proxmox is on my list to get to know the software :)
Lots of people using it which might not be for no reason 😄
How would it look like the compose file if Uptime-Kuma exists already as a service in the server ? Great Tuto though !
Can you elaborate on that?
So you mean if the Uptime-Kuma service existed in another docker-compose file and then add the backup service?
please do a restore video too
There you go :)
czcams.com/video/FPiS6Cck4l0/video.html
5:31 i wonder you ready only mount the docker socket. Can it then even interact with the containers?
11:44 and I hope that values are not valid anymore when the video goes online 😅
My backup strategy is still in concept state. Currently I redundant store my important data on all servers for redundancy for a hardware failure. But that sounds nice ❤
Edit: And I use resilio sync containers for that
You can try :-) But I made sure to disable this account 😜
The read only mode is just enough to interact with the docker socket. You are then just not able to modify the socket file itself
@@techwithmarco I have to admit: I’m pretty new to docker, but for example, watchtower needs access to the socket to affect the other containers. How does this work in this case with a read only mode? 🤔
@@TheOnlyEpsilonAlpha I think a might be wrong about the docker socket. I just got a comment under my traefik video, that there are other ways to use to docker sockert. Just google for docker-socket-proxy and there is a nice project on github which restrict access to the docker api. I'll take a look at it and maybe do another video about it.