Thanks for reaching out to us. We’ve had a few users interested in running haproxy and balena. Check out the starter guides cited in this thread. TL;DR: Users find success in editing/augmenting wifi-connect and creating their own networking config to get this going. Please take a look and let us know how else we can help.
from the logs I would assume that this is not an issue with the CNAME or any domain resolution, but a docker compose / compose runtime.
Checking haproxy.cfg from openBalena the server that haproxy is calling is api:80 which is a local domain.
This local domain api is resolved by the docker engine and links to the service name from here:
As openBalena runs from a ‘forged’ docker-compose.yml file, can you please make sure, that the services have the correct names and that all services are correct.
Can you also please share the docker environment that you use to run the openBalena stack?
If you have any chance can you please share the ‘forged’ docker-compose.yml file with everything blacked that you are concerned about to be published?
I just installed a fresh copy of OpenBalena v3.6.0 on a DigitalOcean Droplet running Ubuntu 22.04.
The only difference from the getting started guide is that I installed the latest version of Docker Compose (v2.6.1) instead of the proposed version (v1.27.4).
I had a similar error to this thread as well as this other thread:
I cannot post my full output of ./scripts/compose logs because the problem is now fixed and I forgot to capture the output before, but basically most of the containers would die instantly.