mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 09:13:02 +03:00
Vaultwarden 1.30.0 not starting on linux/arm #654
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 @har64 on GitHub.
Subject of the issue
vaultwarden not starting on armv6
Deployment environment
Troubleshooting data
/bin/sh: error while loading shared libraries: libc.so.6: ELF load command address/offset not page-aligned
@BlackDex commented on GitHub:
On what platform/host/device are you running this?
@BlackDex commented on GitHub:
Also, what about
latest-alpine?@BlackDex commented on GitHub:
And, which docker version are you running? It should be at least v20.10 if i'm correct. Any version lower is not supported.
@har64 commented on GitHub:
Downloaded Image with portainer, renamed old Container (1.29.1) and started a new one.
@BlackDex commented on GitHub:
Are you sure you are using the latest version?
Did you do a
docker pull vaultwarden/server:latestand removed the previous container, and started a new one?@BlackDex commented on GitHub:
Sound like something else then, since one of the two should at least work i think.
A bit more logs on what is happening would be nice. Docker should also be able to provide a bit more information.
Else, we can't do much with the information we currently have.
@har64 commented on GitHub:
latest-alpine always restarts (no network, no log)
@har64 commented on GitHub:
WD MyCloudEx2Ultra/debian
running (V1.29.2)
docker v20.10
@BlackDex commented on GitHub:
Are you running
latest-alpine? Have you tried that image?@Natherul commented on GitHub:
maybe not the same issue, not sure but I got this today when trying to update my warden instance.
In my case Im running portainer and the error I get from it is
'failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/entry.sh": stat /usr/bin/entry.sh: no such file or directory: unknown'Docker version 24.0.7, build afdd53b
Running in raspberry pi. Using vaultwarden/server:latest through portainer
@BlackDex commented on GitHub:
Closing as stale.
If you still think this is a Vaultwarden issue please provide more information and re-open.
@har64 commented on GitHub:
I found the problem.
alpine above 3.17 can't run on my system.
I copied vaultwarden 1.30.1 in a container with alpine 3.17.5 and that works
@BlackDex commented on GitHub:
This is probably a remnant of previous versions. Portainer seems to keep entrypoints defined in an image long long time ago, while this isn't there in the new images, since we do not use the balenalib images anymore.
Check your config and remove the entrypoint and let the image handle it instead of portainer. That will solve your issue.
@BlackDex commented on GitHub:
You say 3.17 doesn't work, but 3.17.5 does? That seems illogical
@Natherul commented on GitHub:
That solved my issue. I was not aware of this behavior in portainer and indeed in the options for it it had saved old values and set them to override default with it. Thanks
@BlackDex commented on GitHub:
Ow, wait above 3.17
@har64 commented on GitHub:
I say beginning with 3.18 alpine isn't running
@Actuario commented on GitHub:
I removed the entrypoint, leaving the field blank and selecting override, but the error persists
Do I have to do something else to delete the entrypoint?
thank you!
@BlackDex commented on GitHub:
Strange, since what it starts is just a basic Alpine image of which almost nothing is used, except curl and sh.
You can't even run a simple plain Alpine image by it self?
@har64 commented on GitHub:
Yes, i've e.g. downloaded alpine:latest, which is not running