mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Docker image for aarch64 not available #90
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 @Proximyst on GitHub (Sep 16, 2018).
I set up mprasil/bitwarden:raspberry on Docker with the commands listed. When it starts, it instantly exits with error 139 and no logs.
What does this error mean and how may I go around it? Would it be possible to log the errors' actual meaning? Possibly other logs too, if those aren't already there?
@mprasil commented on GitHub (Sep 16, 2018):
Can you post output of
uname -mpi? The image is compiled forarmhfI wonder if it's notarm64vsarmhfincompatibility. Can you try starting the container with-tiinstead of-dto start in foreground?@Proximyst commented on GitHub (Sep 23, 2018):
Sorry for the late answer. Here is the output (which from Bitwarden's side is nothing):
@mprasil commented on GitHub (Sep 24, 2018):
Can you check the architecture differences? I've posted the commands above.
@Proximyst commented on GitHub (Sep 26, 2018):
@mprasil That's what I did in the above snippet (
--name bitwarden -ti --netfor -ti and bottom command for uname)@mprasil commented on GitHub (Sep 26, 2018):
Ah sorry, totally missed that! Yeah, it looks like you're on
aarch64platform, but the image is built forarmhf. You'll have to compile a binary for your platform unfortunately. If I'll have some free time, I might look into makingaarch64image, shouldn't be too hard hopefully.@mprasil commented on GitHub (Sep 28, 2018):
Hi @Proximyst, I've built aarch64 image,
mprasil/bitwarden:aarch64-beta, can you test it if it works for you?@Proximyst commented on GitHub (Sep 28, 2018):
It boots, and I'll test it out further in a second! @mprasil
@Proximyst commented on GitHub (Sep 28, 2018):
Update: Upon trying to create an account, it just yells at me with an "Unexpected error", with no output to docker, nor in the browser console.
@mprasil commented on GitHub (Sep 28, 2018):
Hmm, can you check in developer tools on the network tab if you see any failing requests?
@dani-garcia commented on GitHub (Sep 28, 2018):
Are you by any chance using Chrome and HTTP only? You might need to try other browsers, we've had some problems with that case before.
@Proximyst commented on GitHub (Sep 28, 2018):
It was a badly set up NGinx configuration, actually. It works fine now. Thanks a lot for the work! <3