hassio-zigbee2mqtt: Edge version doesn't launch anymore (fatal: can only run as pid 1)
Description of problem: Edge version fails to launch
Zigbee2mqtt add-on version (if edge, please report commit hash):
Edge
Running platform (details from Suypervisor > System)
Core: core-2022.2.9
Supervisor: supervisor-2022.05.1
Operating System: Home Assistant OS 7.4
Your logs from Home Assistant Supervisor
s6-overlay-suexec: fatal: can only run as pid 1
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 52 (6 by maintainers)
Commits related to this issue
- Base image updates for s6 v3 and pin to 3.14 (#337) * Fixes for s6 v3 and pin to alpine 3.14 * Update version and changelog — committed to zigbee2mqtt/hassio-zigbee2mqtt by mdegat01 2 years ago
The fix is not simple, but if you want to use the edge version I fixed, point your HA repo to https://github.com/thardie/hassio-zigbee2mqtt and install the edge version. I will not be keeping this up to date, so as soon as this is fixed upstream, you will need to switch back.
Problem localised, buggy dependency got downgraded
https://github.com/pirxpilot/connect-gzip-static/issues/16
Just tested, it’s working (please follow the instructions when updating)
I had to uninstall, remove the repository, reboot the host the add repo and install. Now it works.
I just checked and getting from this official repo and installing the edge version now work (above commit fixed it for me)
Same here, cannot run the Edge version so I’ve switched to the main branch, but get some devices that aren’t recognized.
Waiting for the fix, thank for your awesome work guys.
@thardie I think that might just be a frontend bug in Z2M. I found this, looks the same. It is still the edge version so that can happen.
@thardie in your fork you still list the same image as the one here. So your fork isn’t really testing anything, you’re just using whichever one of these images matches your architecture.
To test the branch you would have to pull it into your
/addonsfolder and merge thecommonfolder andzigbee2mqttorzigbee2mqtt-edgefolders to make a normal addon that supervisor can build an image for. Then removeimagefrom theconfig.jsonso supervisor does build a new image and doesn’t just use the one from dockerhub. Or you’d have to adjust the CI in your fork so you can actually publish your own images to dockerhub and then adjust theconfig.jsonto use them.Figured it out. So the steps in the blog are still valid for fixing this addon, add
init: falseand modify files to be executable.The extra problem is that this addon doesn’t have a
build.yamlfile and isn’t pinning the version of its base image. Latest for the alpine base image is now 3.15 and this addon doesn’t work on 3.15. It needs abuild.yamlpinning the version to 3.14 until the application an be updated to work on 3.15. This part isn’t related to s6 v3 it just happened to bite at the same time. I’ll put in a PR for all the above.