Docker: FailureMessage Object: 0xbecc760c

[x1unix]

Type: Bug Report

• Try to follow the update procedure described in the README and try again before opening this issue.

Your Environment

• Hardware: Raspberry Pi 4 (3 GB)
• OS: Raspbian GNU/Linux 10 (buster)
• Docker version: 18.09.1, build 4c52b90

Summary

Hello, I'm trying to run flood in a Docker on my Raspberry Pi 4 and container doesn't start. I just get this error:

$ docker run -it jesec/flood --help 

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbea9060c

I googled a bit to get some context about this error and looks like it's related to a nodejs itself (see: nodejs/node#13922)

Steps to Reproduce

1. Get a Raspberry Pi 4 with latest Raspbian and installed Docker
2. docker run -it jesec/flood --help

[WDaan]

FYI I just re-build the image starting from node:lts-alpine instead of node:alpine & it works fine

[x1unix]

@x1unix thank you

[WDaan]

Maybe don't close yet until actually resolved?

[jesec]

I can't reproduce this on my computer (amd64).

[WDaan]

Only occurs on RPI's! (tested on both RPI3 & RPI4)

[jesec]

32-bit arm?

[WDaan]

Jup :) (I think)

[jesec]

My bet is that Node.js has some sort of bugs on the architecture. The architecture is not going to be used in production, so that's not unexpected.

As a reminder, new RPIs can run 64-bit OS, which brings significant performance improvements and better support from applications. 32-bit is on the way out, and I am afraid that I can't help with that.

If this is confirmed to be a armv7 (32-bit arm) only problem, I will have to drop armv7 from the supported architecture.

[WDaan]

Both my Pi's are running armv7l at the moment

& sure, I can just rebuild with lts-alpine for now

[jesec]

Both my Pi's are running armv7l at the moment

& sure, I can just rebuild with lts-alpine for now

Maybe the upstream fixed the problem. In that case, a rebuild is required to pull the good Node.js binary. The issue would be gone in the next Flood release w/ a rebuild.

I would still recommend you to switch to 64-bit.

[x1unix]

@jesec afaik by default raspberry Pi uses 32-bit repos because they have one OS for all versions and 64-bit version is still unstable.

Probably a solution is to use Ubuntu instead.

[stugr]

I fixed this with:

$ 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

Taken from this thread Koenkk/zigbee2mqtt#7662 (comment)

[cydjohn]

I got the same error on my raspberry pi 3+:

#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0x7ea6e24c

I was trying to run an express server on it with node:14.17.3-alpine3.14
Fix it by change the node version to 16: node:16