You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So in a nutshell, if you create a systemd-container from a Dockerfile, then you have to always add --systemd=always, otherwise the image will fail to start with the rather unhelpful message:
🕙[ 16:43:33 ] ❯ podman run --rm -it localhost/me/init:latestFailed to mount tmpfs at /run: Operation not permitted[!!!!!!] Failed to mount API filesystems.Exiting PID 1...
The text was updated successfully, but these errors were encountered:
If you build a container from a
Dockerfile
in the Open Build Service and specify systemd as theCMD
orENTRYPOINT
as follows:CMD /usr/lib/systemd/systemd
then you obtain the following entry in the container inspect:
Unfortunately, this breaks podman's systemd detection, which relies on the config looking like this:
So in a nutshell, if you create a systemd-container from a Dockerfile, then you have to always add
--systemd=always
, otherwise the image will fail to start with the rather unhelpful message:The text was updated successfully, but these errors were encountered: