Yes exactly, systemd won't be running, and you'll likely have a difficult time starting it in a build-context. I'm pretty sure it requires a plethora of special mounts (like sys and proc) in addition to "other stuff" (search 'init' and 'systemd' in 'podman run' man page). Lastly just to reiterate: You cannot predict the container runtime options at build time, so shouldn't assume them either. Heck, the image could be a base-image for something else, that provides other needed runtime bits. It's far more reliable to simply create the symlinks yourself during the build. Do your runtime status checks and testing, at runtime. Not build time, it's the wrong context. --- Chris Evich (he/him), RHCA III Senior Quality Assurance Engineer If there's a "hard-way", I'm the first one to implement it. On 9/21/23 10:49, Johannes Kastl wrote:
On 21.09.23 at 15:22 etc@balosh.net wrote:
Hi Chris thanks, but actually the `systemctl enabled` line works perfectly the `systemctl status httpd` is the problem.
My guess would be that the "enable" just does a simple link but needs to running D-Bus session, while the "status" requires that. As there is no running system where should it come from?
You could test it "systemctl is-enabled foo.service" works.
Kind Regards Johannes
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io