From 2ff48ac7d6db30728a445a67d95c185e7eaf6b15 Mon Sep 17 00:00:00 2001 From: louis Date: Wed, 29 Jul 2026 16:34:02 +0200 Subject: [PATCH] Boot systemd as PID 1 in the default molecule docker config The default molecule-config never set an explicit command for the docker platform, so the docker driver's own keep-alive default (a bare sleep loop) ran as PID 1 instead of the test image's actual CMD (["/lib/systemd/systemd"] for geerlingguy/docker-*-ansible images). Consuming repos relying on systemd/systemctl in their converge or prepare playbooks (e.g. systemli/ansible-role-userli#136) failed with "Service is in unknown state" because systemd never booted: /run/systemd/system was missing and `systemctl is-system-running` reported "offline". Set command explicitly to /lib/systemd/systemd so the image boots its real init regardless of the docker driver's default behavior. Co-Authored-By: Claude Sonnet 5 --- .github/workflows/ansible-integration-workflow.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/ansible-integration-workflow.yaml b/.github/workflows/ansible-integration-workflow.yaml index 18d6681..25e001e 100644 --- a/.github/workflows/ansible-integration-workflow.yaml +++ b/.github/workflows/ansible-integration-workflow.yaml @@ -29,6 +29,7 @@ on: platforms: - name: instance image: "geerlingguy/docker-\$\{MOLECULE_DISTRO:-debian13\}-ansible:latest" + command: "/lib/systemd/systemd" volumes: - /sys/fs/cgroup:/sys/fs/cgroup:rw - /var/lib/containerd