Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

OKD 3.11 selinux version broken? #39

Open
SteffenSeckler opened this issue Dec 17, 2018 · 6 comments
Open

OKD 3.11 selinux version broken? #39

SteffenSeckler opened this issue Dec 17, 2018 · 6 comments

Comments

@SteffenSeckler
Copy link

Wasn't able to get the new SELinux based version running.
I ran into the following problems, when trying to get it started. Apparently some selinux error (running in project kube-system):

container_linux.go:247: starting container process caused "process_linux.go:364: container init caused \"write /proc/self/task/1/attr/exec: invalid argument\""

ls -dZ /dev/nvidia*

crw-rw-rw-. root root system_u:object_r:container_file_t:s0 /dev/nvidia0
crw-rw-rw-. root root system_u:object_r:container_file_t:s0 /dev/nvidiactl
crw-rw-rw-. root root system_u:object_r:container_file_t:s0 /dev/nvidia-modeset
crw-rw-rw-. root root system_u:object_r:container_file_t:s0 /dev/nvidia-uvm
crw-rw-rw-. root root system_u:object_r:container_file_t:s0 /dev/nvidia-uvm-tools

The old serviceaccount/scc based version is running fine.

System

OKD v3.11
CentOS 7.6.1810

@jeremyeder
Copy link
Member

We have updated instructions for 3.11 that include some simplification in this area. @zvonkok are they ready to be posted?

@SteffenSeckler
Copy link
Author

any update here?

@SteffenSeckler
Copy link
Author

don't want to be impatient, but do you have those instructions available? would also volunteer to test, if the need is there ;) @jeremyeder @zvonkok

@rob-baron
Copy link

I am getting the same error when I try to run a GPU enabled container in OpenShift.

Is there a work-a-round or instructions available?

@SteffenSeckler
Copy link
Author

don't use the current master, 229513e still works (at least somehow).
afterwards they have changed a few things to switch to selinux, but never updated or published the appropriate documentation for that...

@zvonkok
Copy link

zvonkok commented Apr 11, 2019

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants