Always fail to do S2I binary workflow with cluster-admin role due to "cannot exec into or attach to a privileged container"

Solution Verified - Updated -

Issue

Always fail to do S2I binary workflow with cluster-admin role

 [ERROR] Failed to execute goal org.jboss.redhat-fuse:fabric8-maven-plugin:7.5.0.fuse-sb2-750029-redhat-00003:build (default) on project fuse-demo: Failed to execute the build: Unable to build the image using the OpenShift build service: Failure executing: POST at: https://xxx:xxx/xxx/build.openshift.io/v1/namespaces/xx/buildconfigs/fuse-demo-s2i/instantiatebinary?commit=. Message: Internal error occurred: pods "fuse-demo-s2i-1-build" is forbidden: cannot exec into or attach to a privileged container. Received status: Status(apiVersion=v1, code=500, details=StatusDetails(causes=[StatusCause(field=null, message=pods "fuse-demo-s2i-1-build" is forbidden: cannot exec into or attach to a privileged container, reason=null, additionalProperties={})], group=null, kind=null, name=null, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Internal error occurred: pods "fuse-demo-s2i-1-build" is forbidden: cannot exec into or attach to a privileged container, metadata=ListMeta(_continue=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=InternalError, status=Failure, additionalProperties={}). -> [Help 1]

part of events

1m          1m           1         fuse-demo-s2i-xxx         Build                                      Normal    BuildCancelled   build-controller fuse-demo-s2i-3 has been cancelled

Environment

  • Red Hat Fuse
    • Fuse on OpenShift
  • OpenShift Container Platform 3.11

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