If you’re already using a VM anyway (especially for the backend/web UI piece) restoring the image won’t be any different for a server running docker vs one running apt packages.
Easier for me to add a vm in my current system to handle backup, rollbacks and system updates. I’m much more confident that I can quickly restore a vm to new hardware f.e. Which feels important for a password vault.
Thanks a lot for the passbolt recommendation. Gonna look into it now!
AbidanYre@lemmy.world 4 months ago
anamethatisnt@lemmy.world 4 months ago
True, I could use VM+Docker as you say. I’ve been thinking of making a dedicated “Docker VM” before when I’ve looked at interesting projects that has no other offerings.
I’ve felt that using docker in a vm robs docker of it’s advantages so why use it at all if I’m planning on having a vm? I guess one answer is “because the software you want is delivered as a docker image”.AbidanYre@lemmy.world 4 months ago
It may seem like unnecessary overhead, but dockerized vaultwarden in a VM has been a huge improvement for me compared to unix-pass.
And with the volumes set up right, moving it is as easy as copy/pasting the folder it all lives in.
anamethatisnt@lemmy.world 4 months ago
Would work if it was planned to be a system used by only techies or if we knew exactly what groups are wanted beforehand. Definitely gonna remember the tip, splitting it into several shared dbs didn’t even hit me as an option.
constantokra@lemmy.one 4 months ago
FYI, if you run vaultwarden using docker compose with your data volume as a folder, all you have to do is bring it down for like 1minute, make a backup of the folders, and bring it back up. I use a cron script to do this nightly. When my vps host went out of business, I restored my docker folder to a new vps and was up and running again in a couple minutes. Also, you could easily restore it to a virtual machine, if you like. Docker with compose is extremely portable.
wreckedcarzz@lemmy.world 4 months ago
Stupid q but why is the stop/start necessary? I’m running VW (and a dozen other things) thru docker on a synology dsm and it performs backups daily+monthly. Is it actually necessary to stop the container just to copy it?
constantokra@lemmy.one 4 months ago
I’ve read that best practice is to do a database dump, in addition to backing up all the data files. It’s my understanding that there’s a slight chance of corrupting something in the database if you don’t stop the service first, since something could be changed while you’re doing your backup.
The easiest solution for me, as well as for being able to just restore my files and start the service again somewhere else, is to stop, backup, and restart. It’s down for less than 5 minutes while i’m asleep. If I expected better uptime than that I wouldn’t be trying to self host.