starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[SOLVED] Docker image (debian based) v1.29.2 does not start on armv6 systems #1683

New Issue
Closed
opened 2026-02-05 01:29:31 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 01:29:31 +03:00
Owner
Copy Link

Originally created by @BlackDex on GitHub (Sep 3, 2023).

Originally assigned to: @BlackDex on GitHub.

We have discovered that the latest stable version of Vaultwarden has some issues starting on armv6 based systems.

The reason is yet unclear. The only change which is done is the change from Debian Bullseye to Bookworm which probably causes this issue. But we are looking into this specific issue.

In the mean time we suggest to use the alpine based images instead.
So either use:

  • vaultwarden/server:latest-alpine for stable/latest
  • vaultwarden/server:testing-alpine for testing

If you really do not want to use Alpine based images, you must revert back to 1.29.1.

Originally created by @BlackDex on GitHub (Sep 3, 2023). Originally assigned to: @BlackDex on GitHub. We have discovered that the latest stable version of Vaultwarden has some issues starting on armv6 based systems. The reason is yet unclear. The only change which is done is the change from Debian Bullseye to Bookworm which probably causes this issue. But we are looking into this specific issue. In the mean time we suggest to use the `alpine` based images instead. So either use: - `vaultwarden/server:latest-alpine` for stable/latest - `vaultwarden/server:testing-alpine` for testing If you really do not want to use Alpine based images, you must revert back to 1.29.1.
OVERLORD added the bug label 2026-02-05 01:29:31 +03:00
OVERLORD commented 2026-02-05 01:29:35 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Oct 23, 2023):

This issue has been fixed with the testing tagged images released since October the 23th 2023.

@BlackDex commented on GitHub (Oct 23, 2023): This issue has been fixed with the `testing` tagged images released since October the 23th 2023.
OVERLORD commented 2026-02-05 01:29:40 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Nov 3, 2023):

Reopen so users can see this in the issues, but it has been solved in testing as stated above.

@BlackDex commented on GitHub (Nov 3, 2023): Reopen so users can see this in the issues, but it has been solved in `testing` as stated above.
OVERLORD commented 2026-02-05 01:29:45 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Nov 20, 2023):

Closing as fully fixed. All container registries now have the correct working versions.

@BlackDex commented on GitHub (Nov 20, 2023): Closing as fully fixed. All container registries now have the correct working versions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear 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
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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