Closed DanielWeigl closed 2 years ago
Same happens for node-red:3.0.0-18
root@pi:~# docker run -it --rm --name mynodered nodered/node-red:3.0.0-18
Unable to find image 'nodered/node-red:3.0.0-18' locally
3.0.0-18: Pulling from nodered/node-red
6366ba92f08e: Already exists
480d0242e804: Pull complete
e54759dcfc01: Pull complete
1d417e2e963f: Pull complete
06a5294c6966: Pull complete
a1c1895c725c: Pull complete
a829bea8b741: Pull complete
4f4fb700ef54: Pull complete
1b190ab5b65b: Pull complete
346e545bd5a0: Pull complete
4b43fe8f1963: Pull complete
c467b9746df9: Pull complete
f850124c1415: Pull complete
8461b42bb579: Pull complete
Digest: sha256:3ed2da1f95bb3fa1c9b69afd5b34297862bda50471750f13d447adb5104d8eb8
Status: Downloaded newer image for nodered/node-red:3.0.0-18
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe9b047c
But node-red:2.2.2
is still working:
root@pi:~# docker run -it --rm --name mynodered nodered/node-red:2.2.2
Unable to find image 'nodered/node-red:2.2.2' locally
2.2.2: Pulling from nodered/node-red
Digest: sha256:e131dcadfe9297fa8f24233d7ab65b9f116439c868b01cee4c18adef9d9db0a5
Status: Downloaded newer image for nodered/node-red:2.2.2
> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
15 Jul 12:50:45 - [info]
Welcome to Node-RED
===================
15 Jul 12:50:45 - [info] Node-RED version: v2.2.2
15 Jul 12:50:45 - [info] Node.js version: v14.18.2
15 Jul 12:50:45 - [info] Linux 5.10.103-v7l+ arm LE
15 Jul 12:50:46 - [info] Loading palette nodes
15 Jul 12:50:47 - [info] Settings file : /data/settings.js
15 Jul 12:50:47 - [info] Context store : 'default' [module=memory]
15 Jul 12:50:47 - [info] User directory : /data
15 Jul 12:50:47 - [warn] Projects disabled : editorTheme.projects.enabled=false
15 Jul 12:50:47 - [info] Flows file : /data/flows.json
15 Jul 12:50:47 - [warn]
...
15 Jul 12:50:47 - [info] Server now running at http://127.0.0.1:1880/
15 Jul 12:50:47 - [info] Starting flows
15 Jul 12:50:47 - [info] Started flows
What version of docker are you running? also can you confirm you are running a 32bit version of the Raspberry Pi OS?
Probable duplicate of https://github.com/node-red/node-red-docker/issues/296
same problem after update... Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster Linux raspberrypi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux Docker version 20.10.17, build 100c701
Does adding --security-opt=seccomp=unconfined
to the docker run
command work?
Does adding
--security-opt=seccomp=unconfined
to thedocker run
command work?
work! thanks!
@DanielWeigl & @snkku Can you run the following please:
scmp_sys_resolver -a arm clock_gettime64
And update with the output and also see if you can work out what version of libseccomp you have installed
Also check for any OS updates
I don't know if this will be useful but the screen shot is from a Pi4 running Buster with libseccomp2
patched. Shows 3.0.0-14 starting up OK (via docker-compose).
What version of docker are you running?
pi@pi:~ $ docker --version
Docker version 20.10.17, build 100c701
also can you confirm you are running a 32bit version of the Raspberry Pi OS?
yes, its 32bit:
pi@pi:~ $ getconf LONG_BIT
32
pi@pi:~ $ uname -a
Linux pi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
It still fails after installing seccompt and setting clock_gettime64
pi@pi:~ $ sudo apt install seccomp
Reading package lists... Done
Suggested packages:
libseccomp-dev
The following NEW packages will be installed:
seccomp
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.5 kB of archives.
After this operation, 114 kB of additional disk space will be used.
Get:1 http://debian.anexia.at/raspbian/raspbian buster/main armhf seccomp armhf 2.3.3-4 [31.5 kB]
Fetched 31.5 kB in 1s (48.0 kB/s)
Selecting previously unselected package seccomp.
Preparing to unpack .../seccomp_2.3.3-4_armhf.deb ...
Unpacking seccomp (2.3.3-4) ...
Setting up seccomp (2.3.3-4) ...
Processing triggers for man-db (2.8.5-2) ...
pi@pi:~ $ sudo scmp_sys_resolver -a arm clock_gettime64
-1
pi@pi:~ $ docker run -it --rm --name mynodered nodered/node-red:latest
#
# Fatal error in , line 0
# unreachable code
#
#
#
#FailureMessage Object: 0xbe87754c
But this works, as already noted by others:
pi@pi:~ $ docker run -it --rm --name mynodered --security-opt=seccomp=unconfined nodered/node-red:latest
> node-red-docker@3.0.0 start
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
18 Jul 11:22:48 - [info]
Welcome to Node-RED
===================
18 Jul 11:22:48 - [info] Node-RED version: v3.0.0
18 Jul 11:22:48 - [info] Node.js version: v16.16.0
18 Jul 11:22:48 - [info] Linux 5.10.103-v7l+ arm LE
18 Jul 11:22:49 - [info] Loading palette nodes
18 Jul 11:22:52 - [info] Settings file : /data/settings.js
18 Jul 11:22:52 - [info] Context store : 'default' [module=memory]
18 Jul 11:22:52 - [info] User directory : /data
18 Jul 11:22:52 - [warn] Projects disabled : editorTheme.projects.enabled=false
18 Jul 11:22:52 - [info] Flows file : /data/flows.json
...
18 Jul 11:22:52 - [info] Server now running at http://127.0.0.1:1880/
18 Jul 11:22:52 - [warn] Encrypted credentials not found
18 Jul 11:22:52 - [info] Starting flows
18 Jul 11:22:52 - [info] Started flows
...
sudo scmp_sys_resolver -a arm clock_gettime64
is not meant to be a fix, it is a test to see if seccomp supports 64bit time.
The correct solution is upgrade to Bullseye, install the back port mentioned above or run with --security-opt=seccomp=unconfined
Ah, thx - i see.
After installing seccomp2 via
sudo apt-key adv --keyserver hkps://keyserver.ubuntu.com:443 --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
it works - so i guess its nothing you can fix on your side, or? If so, we can close this issue.
Or maybe at least a hint in the main readme so its easier to find?
@hardillb it may be worth pinning this issue in GitHub to hopefully speed up any others finding the fix.
I updated my nodered on my RaspberryPi to
latest
and now it doe not does not run anymore:Steps to reproduce:
Image info:
System info: