The pod is not admitted due to the seccomp issue with anyuid scc - Forbidden: seccomp may not be set

Solution Verified - Updated -

Issue

The pod is not admitted if the anyuid SCC is added to the Service Account and the pod is configured with the seccompProfile setting.

The pod is showing status

Error creating: pods "pod-76f6d7c798-" is forbidden: unable to validate against any security context constraint: [pod.metadata.annotations[seccomp.security.alpha.kubernetes.io/pod]: Forbidden: seccomp may not be set, pod.metadata.annotations[container.seccomp.security.alpha.kubernetes.io/http-echo]: Forbidden: seccomp may not be set]

Environment

  • Red Hat OpenShift Container Platform:
    • 4.11
    • 4.12
    • 4.13
    • 4.14
    • 4.15

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content