-
Vaultwarden Support String0 Vaultwarden Build Version1.32.0 Deployment methodOfficial Container Image Custom deployment methodNo response Reverse Proxynginx Host/Server Operating SystemLinux Operating System VersionNo response ClientsBrowser Extension, Desktop, iOS Client VersionNo response Steps To Reproduce2024/09/27 05:35:26 | stdout | ) Expected ResultWatchtower updated Vaultwarden to the latest image Actual ResultVaultwarden DB exits with error Logs
Screenshots or VideosNo response Additional ContextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
I think PostgreSQL makes it pretty clear why it is not working, you changed the major version from |
Beta Was this translation helpful? Give feedback.
-
I also run into the same problem due to the automatic update via watchtower. Can someone explain what to do now? Thanks and best regards |
Beta Was this translation helpful? Give feedback.
-
Make sure the database is up and running before Vaultwarden starts. You can force a container to wait for an other container to be healthy first. |
Beta Was this translation helpful? Give feedback.
-
If you are running portainer go to stacks/vaultwarden and specify (image: postgres:16) and then redeploy the stack. version: "3.9" |
Beta Was this translation helpful? Give feedback.
If you are running portainer go to stacks/vaultwarden and specify (image: postgres:16) and then redeploy the stack.
version: "3.9"
services:
db:
image: postgres:16