mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Container won't start after update from 1.25 to 1.25.2 #1364
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BJD1997 on GitHub (Sep 24, 2022).
Subject of the issue
Container won't start after update from 1.25 to 1.25.2
After the update my container won't start.
reading the changelog I tried adding the
I_REALLY_WANT_VOLATILE_STORAGE env variable and that fixed the issue with container restart loops.
If I remove this variable it stops working. Before I didn't have this issue
Deployment environment
=========================================================================================
### Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, ADMIN_TOKEN, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY
vaultwarden version: 1.25.2
Install method: docker image
Clients used: iOS, Desktop, Browser-plugin (edge)
Reverse proxy and version: Cloudflare -> NGINX Proxy Manager (jc21/nginx-proxy-manager:latest)
MySQL/MariaDB or PostgreSQL version: no idea?
Other relevant details:
Steps to reproduce
My vaultwarden volume is auto generated by docker a long time ago.
It looks like this: /var/lib/docker/volumes/f9db9550d776d586a3c2eaac1b201856ec625b262f1066ae51f7f6d1bfa444eb/_data
Also the container was update via portainer using the recreate button
Expected behaviour
Container gets recreated with a new image
Actual behaviour
container gets updated and hangs in a restart loop until the I_REALLY_WANT_VOLATILE_STORAGE setting is used and set to true
Troubleshooting data
Logs from portainer:
@BlackDex commented on GitHub (Sep 24, 2022):
See #2656