mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #3872] 1.29.2 docker image not starting up on Ubuntu 20.04 (x84_64) #1700
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1700
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @knightsg on GitHub (Sep 10, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3872
Subject of the issue
After updating to the 1.29.2 image the container continually restarts with the following error (with RUST_BACKTRACE enabled):
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Host system: Ubuntu 20.04.2 LTS
vaultwarden version: 1.29.1 (rolled back from 1.29.2 after it failed to start)
Install method: Docker image (via docker-compose)
Clients used: web vault, android, iOS
Reverse proxy and version: nginx 1.25.2
MySQL/MariaDB or PostgreSQL version: N/A
Other relevant details:
Steps to reproduce
I just updated the version of vaultwarden in my docker-compose file as usual and it didn't work; in the container logs it showed the error outlined in the summary above. Once I identified the issue I reverted the version in the docker-compose file back to 1.29.1 and it started up again without problems.
Expected behaviour
Vaultwarden docker container starts without problems.
Actual behaviour
Container continually restarted and the container logs showed the error specified above after configuring RUST_BACKTRACE in the environment.
Troubleshooting data
This may be the same issue as mentioned in https://github.com/dani-garcia/vaultwarden/issues/3839 but as there's no additional detail in that report I can't be sure.
@BlackDex commented on GitHub (Sep 10, 2023):
Duplicate of:
And no, it's not the same as #3839, if that was the case you wouldn't have seen anything.