"Error: invalid configuration, cannot specify resource limits without cgroups v2 and --cgroup-manager=systemd" #6084
Comments
openshift-ci-robot
added
the
kind/bug
|
Update: this started to happen on my second Fedora 32 machine. On the other hand, I rebooted the first one (due to an unrelated problem :( ) and the problem went away. I'm running Linux 5.6.7 on the still-broken machine, so it's unlikely to be kernel version related. |
|
Can you provide |
|
That one has no $ cat ~/.config/containers/libpod.conf
cat: /home/avi/.config/containers/libpod.conf: No such file or directory
$ podman run -it --rm fedora:32
Error: invalid configuration, cannot specify resource limits without cgroups v2 and --cgroup-manager=systemd |
|
|
|
It's definitely a v2 system from |
|
@rhatdan Does this look like a potential containers.conf issue to you? Maybe a default resource limit specified in the config? |
|
I also bumped into this. First time running podman on Fedora 32, trying to launch a couple of containers. Output:
Other:
|
|
Well, after shutting down the various things and rebooting, it has indeed gone away as per @avikivity mentioning. Hopefully the source of the problem can be fixed since rebooting isn't always convenient. |
Tried it, no change. |
|
Since I needed the machine to work I rebooted it (unfortunately, couldn't check if logout is sufficient since Fedora 32 loses the keyboard/mouse after logout). The problem went away on that machine too. Unfortunately this means I can't help with debugging it until it recurs again (and then I will be limited by needing podman to work). |
|
For me it was an outdated |
|
The reboot part of this seems bizarre... If anyone else encounters this problem: can you try running |
|
I am facing the same issue after upgrading Fedora 31 to 32. Running with debug output yields: Running Previously I removed the directory |
|
Can you provide full output for the command with debugging enabled? Can you try manually setting Finally, does |
|
The command |
|
Alright, I don't think this is Podman. |
|
I'm also seeing this on Fedora 31. |
|
@mheon please change the error message to "could not connect to dbus" then. The current error message looks like it's trying to help, but it's actively misleading. |
|
Digging deeper, that part looks like a bug. We should be discarding resource limits and not erroring unless manually set, but it looks like containers.conf is forcing resources to be set on every Podman invocation. @rhatdan From a brief parse, I'm pretty sure |
|
I see the original error as well when using |
|
I experienced this too on my Fedora 31 laptop (been through 28 > 29 > 30 > 31 upgrades). An inelegant deletion of ~/.config/containers fixed it, but not sure if there are consequences in this. |
|
Most likely you are fine. Podman will just use the defaults if that directory was removed. If you made any customizations, then there could be issues. |
|
I am facing the same issue when using REST API: Error: Any hints? |
|
Did you remove the libpod.conf, and could you try out podman-1.9.2 in updates-testing? |
|
Interestingly, it works with the restart. |
|
Seeing the same issue on two fresh F32 instances, rolling back |
|
I would love to see if people with this issue, see if it is fixed by podman 1.9.2 |
|
I don't believe any are necessary; we'll detect that |
|
hmm, now I'm stumped. So if I don't need to modify the configuration how do I make podman start using cgroups v2? Does that mean I should only have to pass the correct flag to |
|
The system itself needs to be switched to Cgroups v2 - it should be a kernel parameter, though I don't know what the exact parameter is for Ubuntu. |
|
And just to make sure, I know I have cgroups v2 because of the result of but I still need to find a way to switch the system to cgroups v2? It's not enough to have it already installed? Sorry this stuff is pretty foreign to me. |
|
We only support cgroups v2 in unified mode - that is, only cgroup2 will be mounted. |
|
ok managed to follow these instructions https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter, and I tucked in the parameter Is this something else that folks have dealt with? |
|
@giuseppe Any thoughts here? |
|
what version of systemd are you using? The error is coming from crun while trying to create the cgroup. What is the value of the |
|
Thanks for helping out. The version of systemd is 237, and the value of the variable is DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus |
|
it seems like the systemd version is too old. To verify it, try the command |
|
yes that command fails |
|
yes, you either need to upgrade systemd or use the cgroupfs backend for cgroups. What happens is that we are not able to create a systemd scope as rootless while being in a user namespace. |
|
gotcha, I think for the moment I'll switch to a centos 8 machine and see if the same problems arise. But just to try to follow this thread to completion, I tried using --cgroup-manager=cgroupfs and I still got the error that is this issue's title. I've searched a bit but haven't immediately found instructions for setting up cgroupfs, are there specific steps I need to take before I can expect podman to work with cgroupfs? Let me know if we've reached the point where what I'm asking isn't specific to the issue here.. |
|
Please re-open #6798, if you find this unrelated. I closed it for now |
|
I ran into the same issue with a fresh install of Centos 8 even after modifying the kernel parameters so that cgroups v2 was in use for podman. I feel like I'm still not understanding how to make use of the |
|
Still very much present with podman-2.0.1-1.fc32 |
|
Can you provide the error message you're seeing? Also, are you on Fedora or FCOS? |
|
The one in the $subject - after updating from 1.9.3 to 2.0.1 Restart solved it (came to the (obvious) realisation that the recent hardware upgrade and the removal of that supermicro bloat actually makes restarts without upgrades pretty fast.) It did not however resolve everything, I still had to run all the systemd things with: |
|
That's really wierd, because the code path that leads to that error should be completely disabled in v2.0.0 and up... |
|
Another interesting thing, perhaps coincidence, is that |
|
A friendly reminder that this issue had no activity for 30 days. |
|
We had some fixes for this in podman 2.0 releases. Is this fixed now, can we close this issue? |
|
Personally I'm waiting for 2.1.x (stuck on 1.8.2 due to #7016). I'd not encountered this when I was doing 2.x testing though. |
|
Original reporter here, haven't seen it in a long time. On 2.0.3 now. |
github-actions
bot
added
the
locked - please file new issue/PR
and others
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
podman run -it --rm fedora:32Describe the results you received:
Error: invalid configuration, cannot specify resource limits without cgroups v2 and --cgroup-manager=systemdDescribe the results you expected:
#Additional information you deem important (e.g. issue happens only occasionally):
Happens all the time
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Additional environment details (AWS, VirtualBox, physical, etc.):
Fully updated Fedora 32.
The text was updated successfully, but these errors were encountered: