Container does not start

Product support balenaOS
1

Hello,

I pushed 2 container using the cli to a RPI4 device. The images are downloaded successfully and one of the containers starts fine. The other container keeps looping trying to start and goes from installed to starting but never finishes and no errors are shown. Following is a sample of the output in the console:

04.06.20 22:08:59 (-0400) Starting service ‘consul sha256:d374d8a7777208c3918e75db14ea13df35688f642c01e7474ec3ae2fbb14a22d’
04.06.20 22:10:06 (-0400) Starting service ‘consul sha256:d374d8a7777208c3918e75db14ea13df35688f642c01e7474ec3ae2fbb14a22d’
04.06.20 22:12:16 (-0400) Starting service ‘consul sha256:d374d8a7777208c3918e75db14ea13df35688f642c01e7474ec3ae2fbb14a22d’
04.06.20 22:16:33 (-0400) Starting service ‘consul sha256:d374d8a7777208c3918e75db14ea13df35688f642c01e7474ec3ae2fbb14a22d’

Following is the URL to the device and I have granted access for support:
https://dashboard.balena-cloud.com/devices/96f048d63252a70a984fd6ce2dc877bc/summary

I will appreciate any feedback.

Thanks,
Marcelo

2

You assign the consul service to the “edgex-network” but there’s no such network defined in “networks” in your docker-compose.yml file. If you SSH into the host using the Dashboard terminal and run journalctl -fn100 you can inspect issues further.

4

@dfunckt Sorry for I have removed the configuration below as I read somewhere that networks were not supported.
After I added back, is seems to be working and will add the remaining containers to the docker-compose file to make sure it works.

Can you confirm that networks config like the following is allowed? If not, how can I configure to allow all the containers in the device to communicate with each other?

networks:
edgex-network:
driver: “bridge”

Thanks,
Marcelo

5

The driver field is not required int his case, as that’s the default anyway. Simply putting the following should work:

networks:
  edgex-network:

note that in case all your containers will be assigned to the same network, this is actually what implicitly happens when you don’t put any network configuration. This is also what docker-compose does if you run it on your machine