-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
play kube should honor container.seccomp.security.alpha.kubernetes.io #3111
Comments
Hi @AkihiroSuda, thanks for opening the issue! @baude, I also added the |
@weirdwiz Any progress on this? |
There was a failure in podman play when I started working on this, after that I couldn't get a chance to work on this. I shall look into this again. |
@haircommander PTAL |
@haircommander Any progress? |
This issue had no activity for 30 days. In the absence of activity or the "do-not-close" label, the issue will be automatically closed within 7 days. |
Just going to add a comment as this would be a nice to have. |
Yes, I think I will go through some of these play kube issues and implement them. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
Not sure /kind bug or /kind feature.
Probably /kind feature.
Description
play kube should honor
container.seccomp.security.alpha.kubernetes.io
And also
container.apparmor.security.beta.kubernetes.io
Steps to reproduce the issue:
Play-kube the following yaml
Describe the results you received:
Doesn't work because seccomp is not unconfined
Describe the results you expected:
seccomp should be unconfined
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: