4:28 a.m.
Podman doesn't work on Fedora Workstations with GNome-basedGUI. It's a
fact. But How OCI container's cgroups soft machine can work in the forest
of cgroups created by GNome and all GUI applications. Every GUI session has
its own cgroups tree managed by systemd. It is very hard to make a
decision about a parent cgroup for the created container and resource
allocation that doesn't fit every scenario. There are too many variants:
user-session, gnome-terminal, gnome-terminal tab, etc. The server-client
nature of the Gnome GUI will keep the question about a side designated for
resource allocation forever. The Windows WSL and MAC implementation of
Podman follo different approach - creation of the singleton VM running
pre-installed Podman. Fedora workstations have built-in capability to run
VMs via machined and machinectl. The resource limits of this VM can be
easily tuned. Inside the VM OCI containers can be easily managed if the VM
is systemd-based like Fedora's images. User sessions in this VM are plain
remote sessions opened by the user core or core-less.
Such VM can be easily deployed to Fedora WS as a iso copied to btrfs volume.
I tried to run minimalistic smoke-test and got a workable Podman but the
Quemi machine inside Fedora WS for Intel looks slightly exotic. Maybe this
approach is more practical?