-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix seccomp for localhost profiles #202
Comments
@feiskyer I'd like to work on this if you aren't already. Few questions:
|
@runcom Cool and good catch. Seccomp profile is indeed a problem, I think CRI should pass full path to runtimes instead of relative one. Filed kubernetes/kubernetes#36997 to fix this. |
thanks 👍 I'll follow that issue and when done, I'll implement it here in |
@runcom We didn't get a consistent conclusion for kubernetes/kubernetes#36997, and the profile path will be a known issue in kubernetes 1.5, see here. |
@feiskyer thanks, I think we can still support |
+1. |
Let's leave this open until the upstream k8s issue about node's profiles is sorted out. @feiskyer could you change the title here? |
@runcom renamed the title. |
@runcom what is the state of this issue? |
@rhatdan still blocked on kubernetes/kubernetes#46332 |
kubernetes/kubernetes#46332 has been merged for node-local seccomp profiles - however we are still waiting on a seccomp spec I guess kubernetes/kubernetes#39128 |
create-repo-branch.sh: Fix a typo
Seccomp are passed as annotations in CRI. We need to process those keys in annotations and set Seccomp in the runc config.json.
runtime/default
has done (#211). Still waiting for kubernetes/kubernetes#36997:The text was updated successfully, but these errors were encountered: