seccomp=unconfined for a container in a kubernetes pod? Or: changing default in docker 1.10?
I’m running kubernetes with docker 1.10 and I want to run a container with –security-opt seccomp=unconfined . I understand from https://github.com/kubernetes/kubernetes/issues/20870 that seccomp in general is not supported by kubernetes yet, but are there any workarounds?
Do I just need to downgrade docker to 1.9 and lose the security profiles altogether, or is there another way to give my container the access it needs?
Seccomp is disabled by default in kubernetes v1.2 for docker v1.10+, so you should not have problems running container with unconfined policy.
- Database Administration Tutorials
- Programming Tutorials & IT News
- Linux & DevOps World
- Ebook Reviews
- PES Matches, Skills & News