Replies: 2 comments 2 replies
-
I also seem to get the correct cgroup controllers available if I access via an SSH login session, eg. Testing the Plasma X11 login session gives the same broken result, however the IceWM session that came with OpenSUSE is working correctly and lists the |
Beta Was this translation helpful? Give feedback.
-
I move this to a discussion as podman cannot influence how the cgroup in you current env is set up so this does not seem to be a podman bug. |
Beta Was this translation helpful? Give feedback.
-
Issue Description
I'm trying to get going with rootless
podman
andkind
to start trying out a simple kubernetes setup but I couldn't runkind create cluster
due to a missing cpu cgroup controller.Steps to reproduce the issue
These work for me, but I'm not sure exactly how tied to my specific installation they are:
zypper install podman
kind
.This error is being generated because despite delegation actually being configured, the
cpu
andcpuset
cgroup controllers specifically aren't available.I've followed the instructions at both https://kind.sigs.k8s.io/docs/user/rootless/ and https://github.com/containers/podman/blob/main/docs/tutorials/rootless_tutorial.md trying to sort this out.
systemd-run --scope --user kind create cluster
doesn't seem to change anything.Describe the results you received
The needed
cpu
cgroup controller is only available when logging into the system directly using a text terminal.In the graphical session, I can see by tracing up the process tree that the systemd init process has the correct cgroup controllers available but every process beneath it seems be limited to only memory and pids.
Describe the results you expected
Login sessions should have the same cgroup capabilities available regardless of if they are a graphical session or a text session.
podman info output
If I run this in a login session created via a text terminal then
cpu
andcpuset
are listed undercgroupControllers
as well.Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
I'm running KDE on OpenSUSE Tumbleweed. It's late now, and I haven't tested whether it's a KDE issue, a wayland issue or a graphical session issue yet but I wanted to document what I've found so far somewhere at least.
Kernel: 6.8.8
KDE Plasma: 6.0.4
KDE Framework: 6.1.0
Additional information
Podman is overall working, I can run other applications like distrobox or specific containers just fine.
Beta Was this translation helpful? Give feedback.
All reactions