eufy-security-ws: Docker Container 0.5.1 and above crashes during start

Describe the bug
I tried to update to one of the newest versions 0.5.4 of the docker container, but durcng start it crashes with fatal error. I tried 0.5.1 , 0.5.2, 0.5.3 …all the same

Image 0.5.0 does not crash but get the known “token error”

Fatal error in , line 0

 unreachable code
FailureMessage Object: 0xffe6c8ac

Illegal instruction (core dumped)

To Reproduce
Start the Docker container

Expected behavior

Screenshots & Logfiles

Versions:
-docker container 0.5.1 - 0.5.4

Operating system: debian buster

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 15 (5 by maintainers)

Most upvoted comments

Have you checked whether you are complying with these requirements?

I did, and the libseccomp2 version was older (I believe the newest one in debian buster is 2.3.4), so upgrading it to the backported version is a decent workaround. It’s just that having to upgrade the host system for something needed in the container feels entirely wrong. Technically the Debian buster is going to be supported until 2024, so still should be good for another 2 years or so.

Just to confirm that this is the problem we’ve seen above, I have implemented workaround on my system. In case anyone needs it, here’s how to do it if you happen to run Debian Buster on Raspberry Pi or similar:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC 648ACFD622F3D138
echo 'deb http://httpredir.debian.org/debian buster-backports main contrib non-free' | sudo tee -a /etc/apt/sources.list.d/debian-backports.list

sudo apt update && sudo apt install libseccomp2 -t buster-backports

and now the newer alpine image works correctly:

skrobul@pi4:~ $ docker run --rm node:16-alpine3.13 npm -v
8.1.0
skrobul@pi4:~ $

skrobul on Nov 27, 2021