github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-07-17 09:22:30 -05:00
Code Issues 481 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #2563] can't start docker container (latest version on docker hub) #10118

New Issue
Closed
opened 2026-04-20 13:29:48 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 13:29:48 -05:00
Owner
Copy Link

Originally created by @tom-jm69 on GitHub (Jun 18, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2563

Subject of the issue

Deployment environment

  • vaultwarden version: latest from dockerhub

  • Install method: Docker Image

  • Clients used:
    /

  • Reverse proxy and version:
    /

  • MySQL/MariaDB or PostgreSQL version:
    /

  • Other relevant details:
    /

Steps to reproduce

i used, yubico, smtp and nothing more with a docker run command

Expected behaviour

that the container starts without crashing

Actual behaviour

when trying to start the container with the latest vaultwarden docker image, it instantly crashes and in portainer(a webgui for viewing containers), i see that traceback: (logs.txt)

Troubleshooting data

logs.txt
if you do have more questions, please do not hesitate, to ask them

Originally created by @tom-jm69 on GitHub (Jun 18, 2022). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2563 <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- can't start the container anymore on raspbian GNU/Linux 10 (buster), exit code 101 --> ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!--latest from dockerhub --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: latest from dockerhub <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker Image * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> / * Reverse proxy and version: <!-- if applicable --> / * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> / * Other relevant details: / ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> i used, yubico, smtp and nothing more with a docker run command ### Expected behaviour <!-- Tell us what you expected to happen --> that the container starts without crashing ### Actual behaviour <!-- Tell us what actually happened --> when trying to start the container with the latest vaultwarden docker image, it instantly crashes and in portainer(a webgui for viewing containers), i see that traceback: (logs.txt) ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> [logs.txt](https://github.com/dani-garcia/vaultwarden/files/8934445/logs.txt) if you do have more questions, please do not hesitate, to ask them
GiteaMirror commented 2026-04-20 13:29:50 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Jun 18, 2022):

Duplicate of #2497

<!-- gh-comment-id:1159576080 --> @BlackDex commented on GitHub (Jun 18, 2022): Duplicate of #2497
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#10118
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?