You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
podman works, but prints a warning on one of our new boards where we don't have the cpuset cgroup enabled (CONFIG_CPUSET requires CONFIG_SMP and the system we target only has a single core, so we'd rather not build with SMP enabled), and in turn disables cgroup isolation for this system.
Here's the warning:
Failed to add conmon to cgroupfs sandbox cgroup: open /sys/fs/cgroup/libpod_parent/conmon/cpuset.cpus: open /sys/fs/cgroup/libpod_parent/conmon/cpuset.cpus.effective: no such file or directory
There's two things:
the warning is noisy and will make our users ask us what it is about all the time, so we'd eventually need a way to silence it -- for now it's easy enough to pass --cgroups=disabled but if next point is fixed we'll probably want a toggle to keep it quiet?
cgroup ends up disabled despite having everything else it needs, it'd be great if it could work with the cgroups it found instead.
I understand podman doesn't deal with no-SMP systems often, but these still exist and new ones are still made so it'd be great if we could find a way to work around this.
I'm not sure what implications there would be to enable cgroups without the cpuset parts; pkg/cgroups/cpuset.go only copies the cgroup from parent's so it doesn't seem like it'd be such a big deal to skip this one but others have Stat/Apply functions and might be used in places that wouldn't expect the cgroup to be missing... My gut feeling is cpuset is just not used much and could work out the simple "just make this one optional" way -- what do you think?
Steps to reproduce the issue:
build/find a system without cpuset nor systemd
run a podman container
Describe the results you received:
warning displayed
Describe the results you expected:
handle this more gracefully?
Output of podman version:
# podman version
Client: Podman Engine
Version: 4.1.1
API Version: 4.1.1
Go Version: go1.18.5
Git Commit: 428aafd4c2e1b926bb38edfd883257074b981d7c
Built: Fri Aug 5 12:41:43 2022
OS/Arch: linux/arm64
if cpuset.cpus[.effective] file is missing, then ignore the error
since it means the cpuset controller is not enabled in the kernel,
rather than returning an error.
Closes: containers#1134
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
podman works, but prints a warning on one of our new boards where we don't have the cpuset cgroup enabled (
CONFIG_CPUSET
requiresCONFIG_SMP
and the system we target only has a single core, so we'd rather not build with SMP enabled), and in turn disables cgroup isolation for this system.Here's the warning:
There's two things:
I understand podman doesn't deal with no-SMP systems often, but these still exist and new ones are still made so it'd be great if we could find a way to work around this.
I'm not sure what implications there would be to enable cgroups without the cpuset parts;
pkg/cgroups/cpuset.go
only copies the cgroup from parent's so it doesn't seem like it'd be such a big deal to skip this one but others have Stat/Apply functions and might be used in places that wouldn't expect the cgroup to be missing... My gut feeling is cpuset is just not used much and could work out the simple "just make this one optional" way -- what do you think?Steps to reproduce the issue:
build/find a system without cpuset nor systemd
run a podman container
Describe the results you received:
warning displayed
Describe the results you expected:
handle this more gracefully?
Output of
podman version
:Output of
podman info
:The text was updated successfully, but these errors were encountered: