docker compose: Container icinga2-icinga2-1 fails to start

[thomas-maeder]

Hi

Ubuntu 24.04
docker 1.5-2

I have created secrets_sql.env and then tried

docker compose up

Everything seems to come up, but the icinga2 container doesn't really start.

The last lines in docker logs are:

Running hooks in /etc/ca-certificates/update.d...
done.
Site 000-default already enabled
Site icingaweb2-ssl already disabled
Site icingaweb2-ssl-redirect already disabled
Pinging mysql:3306
chown: changing ownership of '/etc/icinga2/features-enabled/checker.conf': Operation not permitted
chown: changing ownership of '/etc/icinga2/features-enabled/notification.conf': Operation not permitted
chown: changing ownership of '/etc/icinga2/features-enabled/mainlog.conf': Operation not permitted
run-parts: /opt/setup/50-icinga2 exited with return code 1

Thanks!

[jjethwa]

Hi @thomas-maeder

Thanks for the report. I'm unable to reproduce the issue locally, can you confirm that the docker version is correct? That seems quite old. For example, my current version from docker --version is: 24.0.7

You may need to install from the docker repo: https://docs.docker.com/engine/install/ubuntu/

[thomas-maeder]

can you confirm that the docker version is correct?

You are right, my bad:

$ docker -v
Docker version 27.4.1, build b9d17ea

[jjethwa]

Thanks for the confirmation. I don't have a similar setup, but I'll work on getting it over the next few days to test with. From where it's breaking, it's the chown of /etc/icinga2, but I'm not sure what the exact cause is. For a quick test, do you mind starting a container manually using docker run -p 80:80 -h icinga2 -t jordan/icinga2:latest to see if that works without issue?

[thomas-maeder]

The docker run command indeed works without issue

[jjethwa]

Great, thanks for checking. That means there might be an issue with the /etc/icinga2 volume when using compose. I should hopefully have more information when I'm able to reproduce your setup.

[skupjoe]

@thomas-maeder are you on the latest branch? Maybe try checking out commit a0000ee (before many of the recent updates .. 🙏 🙏 @jjethwa) and see if this older build works for you?

[thomas-maeder]

@skupjoe Yes. I had done git clone just before docker compose up.

Unfortunately, checking out the older branch doesn't help.

$ git status .
HEAD losgelöst bei a0000ee
nichts zu committen, Arbeitsverzeichnis unverändert

docker compose up ends with this:

[jjethwa]

Hi @skupjoe

Just wanted to check if you are experiencing the issue? I'm having a hard time duplicating it so far.

@thomas-maeder Can you provide some details on your setup?