Invitation to discussion: Is Podman for Linux workstations like Podman for servers or like podman for Windows WSL and Mac?
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?
We've definitely talked about extending Podman Desktop to Linux (in addition to Windows and Mac) and I "think" this would solve your problem. Also, have you tried using Cockpit to manage containers instead of something in the Gnome GUI? On Mon, Jun 20, 2022 at 5:30 AM Pavel Sosin <pavel.sosin@gmail.com> wrote:
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? _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
-- <https://www.redhat.com/en/about/press-releases/red-hat-defines-new-epicenter-innovation-red-hat-enterprise-linux-9> Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
+Stevan Le Meur <slemeur@redhat.com> On Tue, Jun 21, 2022 at 10:53 AM Scott McCarty <smccarty@redhat.com> wrote:
We've definitely talked about extending Podman Desktop to Linux (in addition to Windows and Mac) and I "think" this would solve your problem. Also, have you tried using Cockpit to manage containers instead of something in the Gnome GUI?
On Mon, Jun 20, 2022 at 5:30 AM Pavel Sosin <pavel.sosin@gmail.com> wrote:
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? _______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
--
Scott McCarty Product Management - RHEL Server Email: smccarty@redhat.com Phone: 312-660-3535 Cell: 330-807-1043 Web: http://crunchtools.com
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io
-- Preethi Thomas She/Her Manager, Containers Red Hat <https://www.redhat.com/> pthomas@redhat.com M: 919.633.9500 <https://www.redhat.com/>
participants (3)
-
Pavel Sosin -
Preethi Thomas -
Scott McCarty