Skip to content
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

Usernamespaces: volume mount failing and then container creation failing #1939

Closed
vikaschoudhary16 opened this issue Dec 2, 2018 · 1 comment · Fixed by #1940
Closed

Comments

@vikaschoudhary16
Copy link
Contributor

Description

container create failed: container_linux.go:344:
 starting container process caused "process_linux.go:424: 
container init caused \"rootfs_linux.go:58: mounting \\\"/var/lib/kubelet/pods/8e074cfe-f653-11e8-b0c9-c85b7602acf8/volumes/kubernetes.io~secret/default-token-vjpht\\\" to rootfs \\\"/run/crio/intermediate-mount401612839/root\\\" at
 \\\"/run/crio/intermediate-mount401612839/root/run/secrets/kubernetes.io/serviceaccount\\\" caused \\\"mkdir /run/crio/intermediate-mount401612839/root/run/secrets/kubernetes.io: permission denied\\\"\""
vikaschoudhary16 added a commit to vikaschoudhary16/cri-o that referenced this issue Dec 2, 2018
When running crio with id-mappings,it fails to create container
due to permission errors.

Fixes: cri-o#1939
Signed-off-by: vikaschoudhary16 <vichoudh@redhat.com>
@rhatdan
Copy link
Contributor

rhatdan commented Dec 3, 2018

Permission denied, I always look for SELinux issues first.
Any AVC's reported?

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

Successfully merging a pull request may close this issue.

2 participants