github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-08-24 23:22:58 -05:00
Code Issues 534 Packages Projects Releases 86 Wiki Activity

Vaultwarden 1.22.1 arm64 (Docker) not starting #1068

New Issue
Closed
opened 2025-11-07 06:56:30 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-07 06:56:30 -06:00
Owner
Copy Link
Copy Source

Originally created by @dude71 on GitHub (Jul 3, 2021).

error while loading shared libraries: /usr/lib/aarch64-linux-gnu/libgssapi_krb5.so.2: invalid ELF header

Originally created by @dude71 on GitHub (Jul 3, 2021). error while loading shared libraries: /usr/lib/aarch64-linux-gnu/libgssapi_krb5.so.2: invalid ELF header
GiteaMirror added the troubleshooting label 2025-11-07 06:56:30 -06:00
GiteaMirror commented 2025-11-07 06:56:31 -06:00
Author
Owner
Copy Link
Copy Source

@BlackDex commented on GitHub (Jul 5, 2021):

I just checked the image, and it seems to run for me using an qemu aarch64 environment.
Also, i checked the libgssapi_krb5.so.2 file which points to libgssapi_krb5.so.2.2 which really reads as an arm64 ELF file. So not sure what happened over there. Could you try it again as a clean image maybe?

@BlackDex commented on GitHub (Jul 5, 2021): I just checked the image, and it seems to run for me using an qemu aarch64 environment. Also, i checked the `libgssapi_krb5.so.2` file which points to `libgssapi_krb5.so.2.2` which really reads as an arm64 ELF file. So not sure what happened over there. Could you try it again as a clean image maybe?
GiteaMirror commented 2025-11-07 06:56:31 -06:00
Author
Owner
Copy Link
Copy Source

@dude71 commented on GitHub (Jul 6, 2021):

Tried again pulling fresh image, same problem. This is happening since 1.22.0.

Platform: RPI4, Linux 5.4.124 #0 SMP Sun Jun 13 22:02:19 2021 aarch64 GNU/Linux
Container runtime: Podman 2.2.1.

Last known working version: 1.21. Container log:

/--------------------------------------------------------------------
| Starting Vaultwarden |

Version 1.21.0
This is an unofficial Bitwarden implementation, DO NOT use the
official channels to report bugs/features, regardless of client.
Send usage/configuration questions or feature requests to:
https://bitwardenrs.discourse.group/
Report suspected bugs/issues in the software itself at:
https://github.com/dani-garcia/vaultwarden/issues/new
--------------------------------------------------------------------/

[INFO] No .env file found.

[2021-07-06 10:56:47.880][start][INFO] Rocket has launched from http://0.0.0.0:80

@dude71 commented on GitHub (Jul 6, 2021): Tried again pulling fresh image, same problem. This is happening since 1.22.0. Platform: RPI4, Linux 5.4.124 #0 SMP Sun Jun 13 22:02:19 2021 aarch64 GNU/Linux Container runtime: Podman 2.2.1. Last known working version: 1.21. Container log: /--------------------------------------------------------------------\ | Starting Vaultwarden | | Version 1.21.0 | |--------------------------------------------------------------------| | This is an *unofficial* Bitwarden implementation, DO NOT use the | | official channels to report bugs/features, regardless of client. | | Send usage/configuration questions or feature requests to: | | https://bitwardenrs.discourse.group/ | | Report suspected bugs/issues in the software itself at: | | https://github.com/dani-garcia/vaultwarden/issues/new | \--------------------------------------------------------------------/ [INFO] No .env file found. [2021-07-06 10:56:47.880][start][INFO] Rocket has launched from http://0.0.0.0:80
GiteaMirror commented 2025-11-07 06:56:31 -06:00
Author
Owner
Copy Link
Copy Source

@dude71 commented on GitHub (Jul 15, 2021):

Sorry my mistake, somehow the podman-graphroot folder got corrupted on the SD card causing this issue. Deleting this folder and pulling everything from scratch solved the problem. This issue can be closed

@dude71 commented on GitHub (Jul 15, 2021): Sorry my mistake, somehow the podman-graphroot folder got corrupted on the SD card causing this issue. Deleting this folder and pulling everything from scratch solved the problem. This issue can be closed
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 labels troubleshooting
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#1068