Running bundle creates "runAsNonRoot" error

[tylerslaton]

What is the URL of the document?

https://sdk.operatorframework.io/docs/building-operators/golang/quickstart/

Which section(s) is the issue in?

"Run your bundle. If your bundle image is hosted in a registry that is private and/or has a custom CA, these configuration steps must be complete."

What needs fixing?

After running the operator-sdk run bundle command the pod seems to fail with the following error:

state:
  waiting:
    message: 'container has runAsNonRoot and image will run as root (pod: "memcached-operator-controller-manager-677d7c7469-5wmp5_default(22ae39f5-9493-497d-a70b-f2d5c3c462fe)", container: manager)'
    reason: CreateContainerConfigError

Which was found by running the following on the pod that was created:

k get po memcached-operator-controller-manager-677d7c7469-5wmp5 -o yaml

Additional context

Here is the Dockerfile generated by the operator-sdk init command

# Build the manager binary
FROM golang:1.16 as builder

WORKDIR /workspace
# Copy the Go Modules manifests
COPY go.mod go.mod
COPY go.sum go.sum
# cache deps before building and copying source so that we don't need to re-download as much
# and so that source changes don't invalidate our downloaded layer
RUN go mod download

# Copy the go source
COPY main.go main.go
COPY api/ api/
COPY controllers/ controllers/

# Build
RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -o manager main.go

# Use distroless as minimal base image to package the manager binary
# Refer to https://github.com/GoogleContainerTools/distroless for more details
FROM gcr.io/distroless/static:nonroot
WORKDIR /
COPY --from=builder /workspace/manager .
USER 65532:65532

ENTRYPOINT ["/manager"]

[asmacdo]

This was hit using: Docker: 20.10.8 OperatorSDK: 1.12 Kubectl: 1.21.4 Kind: 0.11.1

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closing this issue.

In response to [this](https://github.com/operator-framework/operator-sdk/issues/5213#issuecomment-1043586720): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.