Replies: 1 comment 4 replies
-
cgroupv2 doesn't allow you to set swappiness so I suggest you simply remove that setting. The cgroup version is defined globally and depens on the system configuration. I think you can still configure swappiness globally via sysctl. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Issue Description
To update my Containers I recreated them, but after they were created, most couldn't start anymore. 4 out of 7 of my Containers got that Error.
I guess the other Containers do not have a swappiness flag. Or is it possible to globally disable only swapiness since cgroupv2 doesn't allow it. Or should I use cgroupv1 instead, is it posible to set cgroupversion per Container? I tried podman updatebutit requiresthe container to be running.
Everything worked before, I'm not sure if podman used cgroup v2 before or it changed with podman v5 or decided to use it with a kernel update
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Error: OCI runtime error: unable to start container "1b5525031c6f817feb4009377f0f032ce8e0940c8bc5b7382631dc9a7ffe1340": crun: cannot set memory swappiness with cgroupv2
Describe the results you expected
Container starting Successfully
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
OpenSuse MicroOS Podman Container Host Image running as VM in Proxmox
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions