Since 4-23-2022 image container won't start with s6-overlay-suexec: fatal: can only run as pid 1 #434
Comments
|
I have a similar problem since version 2022-04-23 on the RaspberryPi 4 (mage: oznu/homebridge:ubuntu): Back to oznu/homebridge:2022-04-14-debian-arm32v7 works fine! Could that be related ? |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
@mroth - the issue is the The updated version of s6 in the latest container does not seem to like this. I was able to replicate the issue you are facing with |
|
@oznu I don't think that's it - I don't have |
|
@oznu I don't have init: true and it doesn't work for me either. Had to roll back to oznu/homebridge:2022-04-14 homebridge_1 | s6-svscan: warning: unable to iopause: Operation not permitted |
|
Same Problem here |
|
Same problem here! not running anymore? |
|
I had to roll back to 2022-04-03 in order for the container to startup successfully again. |
|
same issue with my setup (RPI3). |
|
Same problem here on a Raspberry Pi 4. "Solved" it by downgrading to 2022-04-14. version: '2'
services:
homebridge:
image: oznu/homebridge:ubuntu
restart: unless-stopped
network_mode: host
environment:
- PGID=1000
- PUID=1000
- HOMEBRIDGE_CONFIG_UI=1
- HOMEBRIDGE_CONFIG_UI_PORT=8581
- TZ=Europe/Berlin
volumes:
- ./persist/homebridge:/homebridgeroot@pi /d/homebridge# docker-compose down
Stopping homebridge_homebridge_1 ... done
Removing homebridge_homebridge_1 ... done
root@pi /d/homebridge# docker-compose up -d
Creating homebridge_homebridge_1 ... done
root@pi /d/homebridge# docker-compose logs -f
Attaching to homebridge_homebridge_1
homebridge_1 | s6-svscan: warning: unable to iopause: Operation not permitted
homebridge_1 | s6-svscan: warning: executing into .s6-svscan/crash
homebridge_1 | s6-svscan crashed. Killing everything and exiting.
homebridge_1 | s6-linux-init-hpr: fatal: unable to reboot(): Operation not permitted
homebridge_1 | s6-svscan: warning: unable to iopause: Operation not permitted
homebridge_1 | s6-svscan: warning: executing into .s6-svscan/crash
homebridge_1 | s6-svscan crashed. Killing everything and exiting.
homebridge_1 | s6-linux-init-hpr: fatal: unable to reboot(): Operation not permitted
homebridge_1 | s6-svscan: warning: unable to iopause: Operation not permitted
homebridge_1 | s6-svscan: warning: executing into .s6-svscan/crash
homebridge_1 | s6-svscan crashed. Killing everything and exiting.
homebridge_1 | s6-supervise s6-linux-init-shutdownd: fatal: unable to iopause: Operation not permitted
homebridge_1 | s6-linux-init-shutdownd: fatal: unable to iopause: Operation not permitted
homebridge_1 | s6-linux-init-hpr: fatal: unable to reboot(): Operation not permitted
homebridge_1 | s6-svscan: warning: unable to iopause: Operation not permitted
homebridge_1 | s6-svscan: warning: executing into .s6-svscan/crash
homebridge_1 | s6-svscan crashed. Killing everything and exiting.
homebridge_1 | s6-linux-init-hpr: fatal: unable to reboot(): Operation not permitted
homebridge_1 | s6-svscan: warning: unable to iopause: Operation not permitted
homebridge_1 | s6-svscan: warning: executing into .s6-svscan/crash
homebridge_1 | s6-svscan crashed. Killing everything and exiting.
homebridge_1 | s6-supervise s6-linux-init-shutdownd: fatal: unable to iopause: Operation not permitted
homebridge_1 | s6-linux-init-hpr: fatal: unable to reboot(): Operation not permitted
homebridge_homebridge_1 exited with code 111 |
|
Similar issue, on RPI3B+ ( Edit: This seems more like a #315. version: '3.8'
services:
homebridge:
image: oznu/homebridge:latest
restart: unless-stopped
environment:
- TZ=Europe/Riga
- HOMEBRIDGE_CONFIG_UI=1
- PGID=1000
- PUID=1000
volumes:
- ./homebridge/files:/homebridge
network_mode: "host" |
I solved the problem by updating libseccomp2 to version 2.5.4-1. pi@raspberrypi:~/homebridge $ sudo dpkg -i libseccomp2_2.5.4-1_armhf.deb After that i pulled the last image (latest) and everything works fine again OS |
That solved it for me as well! Cheers |
I'm using latest buster image on my raspberry pi 4 and libseccomp2:armhf (2.5.4-1) ist not officially available. Instead of downloading the package manually and installing it I would suggest to go the back ports way, which might also update / correct dependency packages: In After next After that the latest container starts normally again, well, not completely, there's one problem right after start: However, everything seems to work normally. Any ideas about this? |
|
Hello,
No sorry, I don’t have any idea
Grtzz Stefan
… Op 28 apr. 2022 om 21:20 heeft DannyB ***@***.***> het volgende geschreven:
@stefan1957
I solved the problem by updating libseccomp2 to version 2.5.4-1. First i downloaded libseccomp2_2.5.4-1_armhf.deb from here http://ftp.debian.org/debian/pool/main/libs/libseccomp/ and moved it to the Rpi in my case to the homebridge directory and followed the step below:
***@***.***:~/homebridge $ sudo dpkg -i libseccomp2_2.5.4-1_armhf.deb (Reading database ... 51531 files and directories currently installed.) Preparing to unpack libseccomp2_2.5.4-1_armhf.deb ... Unpacking libseccomp2:armhf (2.5.4-1) over (2.3.3-4) ... Setting up libseccomp2:armhf (2.5.4-1) ... Processing triggers for libc-bin (2.28-10+rpt2+rpi1) ..
After that i pulled the last image (latest) and everything works fine again
OS Linux raspberrypi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
I'm using latest buster image on my raspberry pi 4 and libseccomp2:armhf (2.5.4-1) ist not officially available. Instead of downloading the package manually and installing it I would suggest to go the back ports way, which might also update / correct dependency packages:
In
sudo vi /etc/apt/sources.list
or
sudo vi /etc/apt/sources.list.d/buster-backports.list
add the following line
deb http://deb.debian.org/debian buster-backports main
and add the keys from Ubuntu's (!) key server (Debian's keyring doesn't contain the backports for buster!?):
sudo bash
gpg --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC
gpg --keyserver keyserver.ubuntu.com --recv-keys 648ACFD622F3D138
gpg --export 04EE7237B7D453EC | sudo apt-key add -
gpg --export 648ACFD622F3D138 | sudo apt-key add -
exit
After next sudo apt update the package can be update per
$ sudo apt install libseccomp2/buster-backports
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '2.5.1-1~bpo10+1' (Debian Backports:buster-backports [armhf]) for 'libseccomp2'
The following packages will be upgraded:
libseccomp2
1 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
Need to get 45.9 kB of archives.
After this operation, 32.8 kB disk space will be freed.
Get:1 http://deb.debian.org/debian buster-backports/main armhf libseccomp2 armhf 2.5.1-1~bpo10+1 [45.9 kB]
Fetched 45.9 kB in 0s (335 kB/s)
Reading changelogs... Done
(Reading database ... 128503 files and directories currently installed.)
Preparing to unpack .../libseccomp2_2.5.1-1~bpo10+1_armhf.deb ...
Unpacking libseccomp2:armhf (2.5.1-1~bpo10+1) over (2.3.3-4) ...
Setting up libseccomp2:armhf (2.5.1-1~bpo10+1) ...
Processing triggers for libc-bin (2.28-10+rpt2+rpi1) ...
After that the latest container starts normally again, well, not completely, there's one problem right after start:
$ docker-compose -f docker-compose.homebridge.yml up
Starting homebridge ... done
Attaching to homebridge
homebridge | s6-rc: info: service s6rc-oneshot-runner: starting
homebridge | s6-rc: info: service s6rc-oneshot-runner successfully started
homebridge | s6-rc: info: service fix-attrs: starting
homebridge | s6-rc: info: service fix-attrs successfully started
homebridge | s6-rc: info: service legacy-cont-init: starting
homebridge | cont-init: info: running /etc/cont-init.d/10-adduser
homebridge |
homebridge | -------------------------------------
homebridge | GID/UID
homebridge | -------------------------------------
homebridge | User uid: 1000
homebridge | User gid: 1000
homebridge | -------------------------------------
homebridge |
homebridge | cont-init: info: /etc/cont-init.d/10-adduser exited 0
homebridge | cont-init: info: running /etc/cont-init.d/20-set-timezone
homebridge | Process Process-1:
homebridge | Traceback (most recent call last):
homebridge | File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
homebridge | self.run()
homebridge | File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
homebridge | self._target(*self._args, **self._kwargs)
homebridge | File "/usr/local/lib/python3.8/dist-packages/tzupdate.py", line 89, in get_timezone_for_ip
homebridge | api_response = json.loads(api_response_obj.read().decode("utf8"))
homebridge | File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
homebridge | return _default_decoder.decode(s)
homebridge | File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
homebridge | obj, end = self.raw_decode(s, idx=_w(s, 0).end())
homebridge | File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
homebridge | raise JSONDecodeError("Expecting value", s, err.value) from None
homebridge | json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
However, everything seems to work normally.
Any ideas about this?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
|
Seems to be a one-time-problem from my testings ... it's gone ... everything's fine. Back to original issue: The last version of libseccomp2 for Buster is 2.3... |
|
I reverted the s6-overlay version back to 2.x - this should fix the issues people are seeing. |
|
@oznu , it now errors again in new image but with different error: Quick search leads to https://forum.inductiveautomation.com/t/docker-container-does-not-start/43915/4 where they refer to requiring to update Update: gave up and updated to Bullseye - everything works fine on Deb11. I guess it was just time to bump the Debian version. |
|
Hi all, |
|
Hi all, |
This might be the solution for people then. You can stay on the As mentioned in: https://forum.inductiveautomation.com/t/docker-container-does-not-start/43915/10
I can't feasibly keep the base image on a 4 year old OS release long term. A base image of Ubuntu 20.04 is required for Node.js 18 that is coming in October. |
|
If you're on a Raspberry Pi and in a pickle (can't backport via
This worked for me:
|
If I could politely ask how do I resolve the same issue on Synology with DSM 7.1? Any workarounds perhaps? I see Oznu point and it is fair enough. Does that mean, at least for now, I'm stuck with 2022-04-14. I see that the PUID and PGID are being used by the latest Homebridge image, are not the same as what I've defined as the env variables being PUID = 100 and PGID = 101. It has worked perfectly for years now. However, the new image generates different PUID and PGID on its own. So, it cannot read the files on my volume storage /homebridge. Which is what the log shows and gets stuck in a loop. |
|
I am able to run this latest version just fine in Docker on a Synology using DSM 7.1. I just rebulit the container last night and it started just fine using these commands: Here is my docker-compose.yml. The key for me was changing "init" to "false" To set the PUID and PGID, I ran this command on the Synology, where the USERNAME is the owner of the folder where I store the homebridge variables:
|
Thanks for your reply. Much appreciated. And yes, setting init: false worked. |
|
As there seem to be multiple solutions to this issue, and not much I can do on my end, I have referenced it in the readme under troubleshooting. |
|
For anyone looking for that solution, I had to add the security_opt: # this option
- seccomp:unconfined |
|
Mine is starting up like this, and I am so much of a Linux newbie, that I can't imagine what to do next: s6-rc: info: service s6rc-oneshot-runner: starting If you find this project useful please STAR it on GitHub: s6-rc: info: service credits successfully started up to date in 2s |
@woodyard you fixed this? |
|
For anyone else having this issue with Raspberry PI 4 + Raspberry Pi OS updating (Source https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/) You might also have to update Docker using |
|
In case it helps someone searching for this issue: Make sure as well that you don't have In your |
and others
Describe Your Problem:
Since latest version pushed to Docker Hub yesterday, container wont start for me with message
s6-overlay-suexec: fatal: can only run as pid 1.Rolling back to previous tag for my architecture (
2022-04-14-aarch64) appears to successfully mitigate the issue, so likely something introduced in recent commits.Logs:
etc.
Docker Start Command:
Configured via ansible, but the syntax here is similar to docker compose so should be fairly explanatory.
Homebridge Config:
{ "bridge": { "name": "REDACTED", "username": "REDACTED", "port": 52133, "pin": "REDACTED", "advertiser": "ciao" }, "accessories": [], "platforms": [ { "name": "Hue", "users": { "REDACTED": "REDACTED" }, "hosts": [ "127.0.0.1" ], "lights": true, "nativeHomeKitLights": true, "nativeHomeKitSensors": true, "nupnp": true, "resource": true, "sensors": true, "platform": "Hue" }, { "name": "Config", "port": 8080, "platform": "config" } ] }Screenshots:
N/A
Environment:
Linux raspberrypi 5.10.92-v8+ #1514 SMP PREEMPT Mon Jan 17 17:39:38 GMT 2022 aarch64 GNU/LinuxlatestThe text was updated successfully, but these errors were encountered: