-
Notifications
You must be signed in to change notification settings - Fork 317
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
crun 1.4+ CreateContainer in sandbox failed for volumeDevices container #917
Comments
could you share the pod spec you've used to create the Kubernetes pods? If it is easy to reproduce for you, would it be possible to run a git bisect on crun to see exactly what commit introduced the problem? |
The Rook container one is basically in the above log but I'll see if I can create a minimal test PodSpec to bring it completely back to the bare minimum that still results in a failure, hopefully somewhere tomorrow. It's not what I'd call hard to reproduce; just switch out crun and Kubernetes either starts these containers successfully or it doesn't (with the above error/logs as a result). There's nothing to change other than the crun version used by the cluster/node that would host said container. |
would it be easier for you to share the config.json that crun creates under |
I have bisected the build between tag 1.3 and 1.4. Had to exclude/mark bad three commits because they didn't even build and am left with commit 4eb1f03 as the first bad one, which sadly was also one that just didn't even build:
|
Thanks for doing this. Could you please tell me the previous commits you have used? I doubt this commit could introduce the regression. Is there an easy way to reproduce the issue with a podman command line? Or share the pod spec and imagd you have used? |
The
|
The commit it gave me before 4eb1f03 was commit 8523d6b and that one was good. The other earlier ones it gave me during the bisect process were good aside from fd0e171 and e6fda97, which didn't build either. Terminal exempt from the bisection (excludes the initial good and bad marking of the 1.3 and 1.4 tag respectively). The first good mark here was for commit 9c014c6
|
Thanks for the extra information. I am out of office next week but I will try to take a deeper look as soon as possible |
fix the creation of devices nodes in the container rootfs. commit d583bdc introduced the regression. Closes: containers#917 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
sorry for the delay, opened a PR here: #960 |
Tried a run with a build of the latest master containing it (3417536) , LGTM 👍 |
Starting with crun 1.4 and up, Kubernetes is unable to initialize containers such as the Rook/Ceph OSD's blkdevmapper initContainer, which are using a volumeDevice. The creation fails with the following set of log messages:
When reverting back to 1.3, they come online normally.
As specifically reverting crun back to 1.3 and not touching anything else resolves this issue, I suspect the problem is with crun.
However, I also don't have much more information to go on at this time so if any other/additional information is desired, I'll gladly receive some pointers on where to look or what info to supply.
The text was updated successfully, but these errors were encountered: