I was trying to deploy Edgex on RPi4 following the https://www.balena.io/blog/make-a-web-frame-with-raspberry-pi-in-30-minutes/ to set up balena CLI, balena cloud etc on my PC, balena Eatcher; i get the docker-compose file for the arm64 and push it into my RPi4, untill this everything was fine, but…

Hi, is it possible to share your code with us (if it’s up on Github, for example)? Would be able to see better what are you doing. Not sure what Edgex is, and hard to comment on that. Do you have any Raspberry Pi 3 boards to try things? I wonder if it’s a 32-bit/64-bit issue (Pi3 balenaOS is by def…

Hi, no, i don’t have RPi3 to try. i loaded a 64bit OS because EdgeX require it. So after this i made push of the docker-compose.yaml, i discovered partially the problem rootcause, it was the field names uncompatible with the version 2 of docker-composer, such as container_name, hostname and network…

Hi @chrisys , yes, but i didn’t find solution there. it says what networking is not working fine, and i commented out the hostname line from mqtt definition, so how i can define the hostname for this service?

BTW, commenting out the same fields for device-random container definition solved the issue. Now this service looks fine.

@Miliks1975 the hostname by default is the service name, so you would rename the service name to the hostname desired - it mentions this in the guide: Due to (6), hostname doesn’t work either. The services are accessible using only the service name as defined in the docker compose . Since Edg…

so, i changed it like this: edgex-device-mqtt: image: edgexfoundry/docker-device-mqtt-go-arm64:1.0.0 ports: - “49982:49982” volumes: - db-data:/data/db - log-data:/edgex/logs - consul-config:/consul/config - consul-data:/consul/data depends_on: - edgex-core-data - edgex-core-command

Let’s ping @odyslam here and see if he can offer any advice since he wrote the tutorial!

Hey, The mqtt device service appears to have a panic error because it can’t connect to the mqtt broker. This question is more edgex related and not balena (I think). You should configure the device-service to point to the broker, either using the right ip or the correct container name.

Edgex on RPi4 using Balena fail to run MQTT&device-random services

Product support

chrisys October 14, 2019, 2:02pm 5

@Miliks1975 did you find this tutorial, which may help: EdgeX + Balena Walkthrough Tutorial

Topic		Replies	Views
EdgeX + Balena Walkthrough Tutorial Project help raspberrypi3 , summary	5	3236	October 17, 2019
edgex foundry multicontainer app crashing balenaOS balenaOS	4	1423	July 5, 2021
How to deploy official eclipse-mosquitto container on a raspberry pi as a service in a docker compose file? Product support docker	6	8594	February 25, 2021
Help getting the "balenaDash" project working Product support raspberrypi3 , balenadash	15	1456	April 30, 2019
Container does not start balenaOS	3	720	June 8, 2020

Edgex on RPi4 using Balena fail to run MQTT&device-random services

Related topics