Closed Smandurlo closed 2 years ago
SOLVED: I created a new image from Dockerfile and uploaded to xxxxxxxx [REMOVED since it is fixed in official images] It is only arm/v6 I hope the next images will be created with v6 included
Thanks for looking into this. Added arm/v6 target https://github.com/zewelor/bt-mqtt-gateway/blob/master/.github/workflows/docker_build.yml#L48
[x] I've read the Troubleshooting Wiki, my problem is not described there and I am already using the specified minimum bluez version.
Describe the bug I am not really able to run the docker /docker-compose version. They were running flawless on 2 raspberry pi zero w, one with buster and another one with bulleye. This morning I decided to make a clean installation from scratch (to upgrade buster and reclaim 10GB wasted space on bulleye), just installed docker and docker-compose, copied the same config.yaml and docker-compose.yaml but I get Exited (139).
The log is empy. Debug is true.
To Reproduce Steps to reproduce the behavior:
Expected behavior To have a running container
Config docker run -d --name bt-mqtt-gateway --network=host --cap-add=NET_ADMIN --cap-add=NET_RAW -v $PWD/config.yaml:/application/config.yaml zewelor/bt-mqtt-gateway
Debug gateway logs run gateway.py with -d switch and paste formatted output log
No log, it is empty
Server (please complete the following information):
Additional context
I tried to return to buster, pulled previous images, tried a docker downgrade with no luck.
EDIT: I think I narrowed down the problem. It seems the arm v6 for raspberry pi zero W is no longer there, only v7. I tried with a raspberry pi3 b and it worked immediately without problems.