mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-01 11:19:52 +03:00
Support armv6 devices like Pi Zero or first Raspberry Pi #240
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 @kennymc-c on GitHub (Feb 23, 2019).
I'm trying to get Bitwarden_rs running on a Raspebrry Pi Zero W. After starting via Docker-Compose the process aborts with Exit Code 139 and no bitwarden log is created. The Docker log looks like this:
Feb 23 19:34:38 pizza dockerd[2573]: time="2019-02-23T19:34:38+01:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/7e16114071bcc98abf42609816b7d949f35329 Feb 23 19:34:41 pizza dockerd[2573]: time="2019-02-23T19:34:41+01:00" level=warning msg="OOM monitoring failed" error="cgroups: memory cgroup not supported on this system" Feb 23 19:34:42 pizza dockerd[2573]: time="2019-02-23T19:34:42+01:00" level=info msg="shim reaped" id=7e16114071bcc98abf42609816b7d949f35329b9b937ff1bc4848816bdb79c8d Feb 23 19:34:42 pizza dockerd[2573]: time="2019-02-23T19:34:42.801427746+01:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDeletePreviously it worked fine on a Pi 3. I found a similar issues (#185) where you should use the aarch64 image. On the pi zero however i get the following error message after startup:
standard_init_linux.go:190: exec user process caused "exec format error"@mprasil commented on GitHub (Feb 23, 2019):
Can you post output of
docker version?@kennymc-c commented on GitHub (Feb 23, 2019):
`
Client:
Version: 18.06.3-ce
API version: 1.38
Go version: go1.10.3
Git commit: d7080c1
Built: Wed Feb 20 02:42:54 2019
OS/Arch: linux/arm
Experimental: false
Server:
Engine:
Version: 18.06.3-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: d7080c1
Built: Wed Feb 20 02:38:25 2019
OS/Arch: linux/arm
Experimental: false
`
@mprasil commented on GitHub (Feb 23, 2019):
And you're using
mprasil/bitwarden:raspberryimage, right?@kennymc-c commented on GitHub (Feb 23, 2019):
right
@mprasil commented on GitHub (Feb 24, 2019):
I think this is due to the fact, that the image is compiled for armv7hf which won't run on pi zero (and RPi 1?) We use
balenalib/armv7hf-debian:stretchfor the raspberry image, which probably won't run on armv6 device. Maybe we could find some other base image for pi 1/zero and create special image for those devices?@kennymc-c commented on GitHub (Feb 24, 2019):
That would be great. I had already thought that the image was designed for armv7 and that's why it came to this problem. It's actually a bit irritating if the image is called raspberry and not running on the still current Pi Zero models.
@mprasil commented on GitHub (Feb 25, 2019):
Hi, would you be able to test
bitwardenrs/dev:armv6image on your pi zero? I tried to build the image for armv6 devices, but don't have HW to test it.Agree, it's mostly for historical reasons. Back then we only supported amd64 (x86) and armv7hf (raspberry pi 2+) so I went with that. Now we have alpine images, aarch64 and hopefully armv6, it's getting a bit complicated. I'm going to document all the options.
@kennymc-c commented on GitHub (Feb 25, 2019):
With
bitwardenrs/dev:armv6i get exit code code 127 with/bin/sh: 1: ./bitwarden_rs: not foundin log@mprasil commented on GitHub (Feb 25, 2019):
Can you try pulling the latest dev image
docker pull bitwardenrs/dev:armv6and try running it again?@kennymc-c commented on GitHub (Feb 25, 2019):
Seems to be working now :) No errors in log but i've only tested the login page so far.
@mprasil commented on GitHub (Feb 25, 2019):
Thanks for testing. I'll create a PR now and once merged will build official image.
@mprasil commented on GitHub (Feb 25, 2019):
Okay, image is now building. Once done, (will take about an hour) it will be available as
mprasil/bitwarden:armv6.@mprasil commented on GitHub (Feb 25, 2019):
If you have a time, once the official image is available, can you please fill in a table at the end of this document? I'm trying to collect all the various boards and what images were tested.