Closed t-8ch closed 9 months ago
Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).
Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.
After that, please reply here with a comment and we'll verify.
Contributors that have not signed yet: @t-8ch
@cla-bot check
Please install it explicitly
Done
With this changeset it's possible to use the container as a Type=notify
systemd service in combination with podman:
# icinga.service
[Service]
Type=notify
ExecStart=/usr/bin/podman run --name icinga --sdnotify container docker.io/icinga/icinga2
[Install]
WantedBy=default.target
This service will only be marked as ready when icinga2 from within the container has signalled its completed startup. This makes it possible to order other systemd services properly in relation to the icinga container. We want to use it to perform some post-start tasks that need the container to be properly started.
podman is able to pass systemd notification sockets through to the containerized application. By enabling the systemd integration in icinga2 the host systemd is able to see the runtime status of the containerized icinga2 instance, especially for startup notifications.
libsystemd is already installed in the base image so no new runtime dependency is introduced.