Re:Vaultwarden: Unofficial Bitwarden compatible server writt...
by MrOwen on Wednesday August 14, 2024 @11:39AM
(#41247348)
I've seen watchtower burn so many people...
Better to put everything in git and run your own renovate bot which will create PRs for you to review and also pull in the changelogs to the PR itself so you can check for breaking changes.
Re:Vaultwarden: Unofficial Bitwarden compatible server writt...
by OptionOfT on Wednesday August 14, 2024 @12:29PM
(#41247933)
Do you have an example online? Always interested to see different approaches.
Re:Vaultwarden: Unofficial Bitwarden compatible server writt...
by mbirth on Friday August 16, 2024 @06:19AM
(#41264991)
Just set Watchtower to quit after run and run it manually when convenient. This way, you’ll instantly know if some update went wrong and can fix it.
Re:Vaultwarden: Unofficial Bitwarden compatible server writt...
by OptionOfT on Wednesday August 14, 2024 @12:26PM
(#41247894)
Please be careful with Watchtower. Its update functionally can not (by design) separate your ENV settings and the ones from the new container.
E.g. you deploy with DATABASE_URL=x
This becomes DATABASE_URL=x PYTHON=3.0.0
You did not set the Python one, the image did via ENV.
Now a new version comes out with PYTHON=3.1.0.
Watchtower doesn't know which ENVs you set and which ones came from the container as docker inspect exposes them in the same way.
So now Watchtower deploys the new version (which only has Python 3.1.0) with DATABASE_URL=x PYTHON=3.0.0.
And stuff stops working.
I use an ansible playbook which maintains the only ENV vars that need to survive an update.
My setup was based on their Docker images, and thinking it was the safest option I had set up Watchtower to automatically update to the latest image nightly to get the latest security patches. But then I discovered that the bitwarden-rs image had not been updated for _months_ because of the rename.
So basically I was hosting my whole password database in this, and I had suddenly lost security updates without realizing.
Btw, I'm not blaming neither Vaultwarden or Bitwarden. But if you're going to self-host something this security critical, just be sure that you definitely monitor it _manually_ to make sure you're not on some unpatched vulnerable version some months down the line.