Alpine 3.13 Tag Containers Don't Start on ARMv7 about rtl_433_docker HOT 7 CLOSED

Hello,

I'm glad you found the docker images useful, this is a known issue. As a workaround I've recently introduced alternative builds based on alpine:3.12 which you have already found in your second example 👍 (see #3 if you want details).

For now the only workaround is to use any image based on alpine 3.12.
You can access those images by hertzg/rtl_433:alpine-3.12-* where * can be any valid rtl_433 version, master or latest respectively.

Example:

$ docker run --rm -it --device /dev/bus/usb/001/005 hertzg/rtl_433:alpine-3.12-latest

I am not sure if the rtl_433 or it's dependencies support alpine and musl so I'm currently working on introducing images built based on debian images and change the :latest tag to target those. The alpine based images would still stay but be an "opt-in" variant.

from rtl_433_docker.

I've just pushed a build pipeline which provides debian builds. Maybe you could give it a try and see if it resolves the issue.

https://github.com/hertzg/rtl_433_docker/actions/runs/565743906

Once the pipeline finishes you can try:

$ docker run --rm -it --device /dev/bus/usb/001/005 hertzg/rtl_433:debian-buster-latest
# or
$ docker run --rm -it --device /dev/bus/usb/001/005 hertzg/rtl_433:debian-bullseye-latest

from rtl_433_docker.

debian-buster-latest worked for me. bullseye throws the same error as alpine.

thank you.

from rtl_433_docker.

you need to install this for the new alpine docker image:

wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.4.4-1~bpo10+1_armhf.deb
sudo dpkg -i libseccomp2_2.4.4-1~bpo10+1_armhf.deb

than it should work ;)

from rtl_433_docker.

dpkg -i

AFAIK Alpine Linux is not a Debian derivative. I’m not sure why that package would be required. If you can elaborate a bit maybe we could whip up a PR for this but so far I don’t see how that is related to the libusb issue.

from rtl_433_docker.

I had this problem also on another alpine docker image. Than i have updated this container, same error, after the installation of this libusb was the container starting again.
I found this info in another chat

from rtl_433_docker.

For people who are still experiencing this or who just endded up here from search engines, you can find the workaround and summary on another issue.

from rtl_433_docker.