-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Jobs that run privileged containers started failing #3673
Comments
Hello @orlangure. Thank you for your report. We will take a look. |
We have the same error when using kind(K8s in Docker) |
@orlangure, Looks like the issue is not with the image - rancher/rancher#33300 . Manually set up
@lukaszo, kind - rancher/rancher#33360 |
@al-cheb, interesting, but the image that I use for tests didn't change for a while (updated 8 months ago), and the tests passed until now. The only change that I noticed in the past days was github actions virtual environment upgrade. From the linked issues it appears that the problem happens not only in github actions, so I assume it could be related to the kernel upgrade or some package that changed recently? |
Yep, that's right the kernel was updated - https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F20210628.1 . |
@orlangure, Could you please update an image to the latest version https://k3d.io/faq/faq/#solved-nodes-fail-to-start-or-get-stuck-in-notready-state-with-log-nf_conntrack_max-permission-denied to test the workaround? |
It contains a fix for kubernetes-sigs/kind#2240 We've hit when running GitHub actions actions/runner-images#3673
Thanks @al-cheb, and sorry for late response. I'll prepare an update for my users to let them know that older k3s versions won't work in Gnomock. |
Description
In gnomock there is an automated test that runs lightweight kubernetes distribution (k3s) inside a docker container. This test passed successfully 5 days ago, and started to fail consistently after the latest github environments upgrade.
The error that occurs inside the container is
but I'm not sure this is the root cause.
I have the same test running on circleci, and it continues to pass.
I have a few other jobs that set up docker containers, and they still work. The difference is that
k3s
job starts a privileged container.Virtual environments affected
Image version and build link
Failed build: https://github.com/orlangure/gnomock/runs/2951632183?check_suite_focus=true
Successful build (5 days ago): https://github.com/orlangure/gnomock/runs/2916092414?check_suite_focus=true
Is it regression?
20210614.1
Expected behavior
No response
Actual behavior
No response
Repro steps
Run
[preset] k3s
job from Gnomock repository.The text was updated successfully, but these errors were encountered: