-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create container with linux 6.2 on ubuntu 22.04 #727
Comments
My error:
|
Hi @rmillet-rs, I tried the installation from zero and worked for me:
I installed everything new in a VM (virtualbox) and followed the documentation minus the shiftfs, I used the branch k6.1: Is not much, but I hope this can help. |
Hi @rmillet-rs, Thanks for reporting; I was unable to repro on my Ubuntu-22.04 host with Sysbox 0.6.2 and Docker 24.0.5. However I am not using the HWE kernel, so I suspect the problem you are facing it's due to that (although @frulio 's comment above seems to suggest it works with HWE too). The error you are getting is a bit strange too:
What's happening here is that during container start, Sysbox was trying to create the Can you try @frulio 's steps (particularly the shiftfs installation) to see if that works? Also, you indicated image Thanks! |
Hello, For info, I initially had the problem on my host then rollbacked the kernel. And reproduced the issue in a VM installed from scratch before opening the ticket. So now, all is done in the VM. Since the last time, I upgraded the system:
In
I then installed shifts (+reboot), but I still get the error with alma 8 image:
I tried a few images, but only almalinux produces the bug. If I am the only one impacted, do not waste your time on it. (I don't need to upgrade my kernel, I did this because I had some issues with my material but as it changed nothing I don't need to stick on this kernel). Thanks |
Hi @rmillet-rs, I was able to reproduce the problem on a freshly provisioned Ubuntu-Jammy host. Turns out it's a bug in the way Sysbox finds the kernel headers in the host machine so that it can bind-mount them (read-only) into containers (since apps running inside Sysbox containers often need them). The bug manifests itself when the host has the kernel headers such as:
Notice how the I'll fix it soon; thanks again for reporting. |
@ctalledo I created a PR @ nestybox/sysbox-runc#91 to try to address this issue |
Fixed in upcoming v0.6.3 release. Closing. |
linux-generic-hwe-22.04
)Hello, with the 6.2.0 kernel, container fails to start (was working with 5.15.0).
This is related to the image, because
docker.io/nestybox/alpine-docker:latest
starts.The text was updated successfully, but these errors were encountered: