zigbee2mqtt
zigbee2mqtt copied to clipboard
Koenkk
Lastest container image doesn't start with no errors on logs.
What happened?
I was using as the instruction recommended "koenkk/zigbee2mqtt" image, which pointed to the latest image. However the latest image fails to start with no errors in logs. The only log message that is shown is "Using '/app/data' as data directory" and immediately the container exits.
My architecture is as following:
uname -a -> Linux ******** 6.8.0-55-generic #57-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 12 23:42:21 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
uname -m -> x86_64
Image architecture should match: sudo docker inspect ghcr.io/koenkk/zigbee2mqtt | grep Architecture "Architecture": "amd64",
Trying to modify the entrypoint and command to run apt update and upgrade results in a segmentation fault:
fetch https://dl-cdn.alpinelinux.org/alpine/v3.21/main/x86_64/APKINDEX.tar.gz Segmentation fault (core dumped)
Downgrading to version 1.42.0 resolves the problem for me
What did you expect to happen?
The latest image starts up
How to reproduce it (minimal and precise)
Just deploy using the "docker" deployment instruction on a 64 bit intel bare metal device, I am using Ubuntu 24.04.1 as the docker server
Zigbee2MQTT version
latest (01 may 2025)
Adapter firmware version
Not relevant
Adapter
Not relevant
Setup
container over x86_64 (ubuntu OS)
Debug log
None, no output from the container
As there is no log, it is hard to provide help.
I would first check this
https://github.com/Koenkk/zigbee2mqtt/discussions/24198
as you have to downgrade to 1.42.0 to have a working version.
You may also have logs entries in an external log file. You need to properly configure this in your configuration.yaml
As I stated above, it seems that the shell doesn't function correctly, and I assume it is an incorrect instruction set for this architecture. Basic commands such as "apt update" trigger a segmentation fault. I tried reverting to the default configuration file (just not mapping it to the volume for example), and it didn't do anything. A simple docker run command with no parameters, no ports, no volumes will still fail.
I expect something is wrong with your Docker setup (I'm also running the amd64 image and it works fine, you would expect a lot of issues report if it would not). Does the hash match the one from Docker hub? https://hub.docker.com/r/koenkk/zigbee2mqtt/tags (also try pulling from Docker hub instead of ghcr.io)
Yes, I saw today that other containers sometimes have issues as well, and I am not fully able to understand why, but it seems the damm overlay2 things is corrupting them. I switched to fuze-overlay and it is stable now. Closing this issue