Why it is impossible to run some containers on some platforms?
Dear colleagues, please, compare CRun and runc implementation. CRun lacks some dependencies like seccomp,etc. Most RedHat UBI, ... images were cut from the distro together with systemd2, logind, resourced, oomd, ... Running bash in the systems with user's sessions managed by systemd2 requires 1. Communication with systemd on the host to put the container cgroup into the right place. 2. Starting the user's session inside the container. You can see it clearly if you pull/from/unshare/mount ubi or fedora image using buildah. /bin/bash in the userspace ,I suppose can run correctly only inside user's session and borrows session's resources. What about annotating "systemd" images and initializing them using systemd by the default?
Hi Pavel, we already setup the container in "systemd mode" when the entrypoint is either /usr/sbin/init or /usr/lib/systemd/systemd. Why would an annotation work better? What cgroup manager are you using for the container? Systemd or cgroupfs? Thanks, Giuseppe Pavel Sosin <pavel.sosin@gmail.com> writes:
Dear colleagues, please, compare CRun and runc implementation. CRun lacks some dependencies like seccomp,etc. Most RedHat UBI, ... images were cut from the distro together with systemd2, logind, resourced, oomd, ... Running bash in the systems with user's sessions managed by systemd2 requires 1. Communication with systemd on the host to put the container cgroup into the right place. 2. Starting the user's session inside the container. You can see it clearly if you pull/from/unshare/mount ubi or fedora image using buildah. /bin/bash in the userspace ,I suppose can run correctly only inside user's session and borrows session's resources. What about annotating "systemd" images and initializing them using systemd by the default?
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
participants (2)
-
Giuseppe Scrivano -
Pavel Sosin