CNAME conf error. Haproxy fail (sorry)

[Winkelmann]

Hello,

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:

s3 is exiting with code 255 after startup with ./scripts/compose up

I really don’t know what’s happening here. It seems like the s3 container dies instantly, so that the registry container follows with code 255 (like the s3 container), so that HAProxy won’t start, because the hostnames could not be resolved (because the containers are no longer there) and the cert container can’t connect to port 80 because of HAProxy not serveing anything at all. s3 dies → registry dies → HAProxy won’t start → nothing Why is s3 exiting? Where can I find the right logs? There …

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.

All this to say that this Github comment mentionned by @aleho (Services crash without log. · Issue #99 · balena-io/open-balena · GitHub) fixed my issue !

echo 'GRUB_CMDLINE_LINUX=systemd.unified_cgroup_hierarchy=false' > /etc/default/grub.d/cgroup.cfg
update-grub
reboot