-
Notifications
You must be signed in to change notification settings - Fork 521
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
GitLab Runner - SELinux Issue #1651
Comments
It appears this is an issue with the |
Thanks for this report @bdwyertech. Happy to keep this open to track this issue but I'm inclined to close it if you're happy with the workaround. If I don't hear back from you, I'll plan on closing in a few days. |
I'll close this. As mentioned, @bdwyertech feel free to re-open if you're not ok with using the |
The alpine image didn't work for me though a year old tag |
Re-opening since it's still an issue for you, @anthr76 - I'm doing some work on the SELinux policy now and will investigate before our next release. |
Thanks @bcressey . The linked gitlab issue has some good context as well. Sadly this seems to mostly boil down to GitLab not exposing the Selinux portion of the pod spec to users. |
This should be fixed as of the 1.3.0 release. |
Image I'm using:
Latest v1.1.2 on EKS 1.20
Also tried going back to EKS 1.19 back to v1.0.x
What I expected to happen:
GitLab Runner should be able to create pods in my cluster.
What actually happened:
GitLab Runner was not able to create pods within my cluster.
How to reproduce the problem:
Deploy the gitlab/gitlab-runner helm chart to test.
It seems like there is an SELinux issue going on here preventing the pod from pulling some of its containers. I think it means its attempting to mount an unlabeled_t tmpfs underneath /local (of type local_t).
Sample Helm Chart Config
Related: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28050
The text was updated successfully, but these errors were encountered: