[Bug]: meshtastic exited with code 134 #4278
habr05
started this conversation in
Troubleshooting
Replies: 1 comment 1 reply
-
Hello, I had the same problem when i try to execute it on raspberry pi zero w. You have to use root user and privileged option while login into the docker because meshtasticd executable need to access to SPI and GPIO Then, you need to create the config.yaml file in the docker file system with correct values with "cat" command because vi or nano is not installed in this image. To finish you use ctrl + D
And then it starts :) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Category
Other
Hardware
Other
Firmware Version
2.3.13.83f5ba01
Description
I build the docker image using instructions from https://meshtastic.org/docs/software/linux-native/#usage-with-docker.
I can fire up the image using
docker run --rm -p 4403:4403 meshtastic/device
. But if I provide a (correctly formatted)config.yaml
containingthe container exits with the following:
Linux-native (meshtasticd_2.3.13.83f5ba0_arm64.deb) on the same hardware, with the above config.yaml, works without issues.
Relevant log output
Beta Was this translation helpful? Give feedback.
All reactions