We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is there any need for the configmap-operator-registry scratch image to run as root? https://github.com/operator-framework/operator-registry/blob/master/configmap-registry.Dockerfile
Can we add this to the image?
# This image doesn't need to run as root user. USER 1001
The text was updated successfully, but these errors were encountered:
Add USER for non-root image usage
091b76d
Fixes operator-framework/operator-registry#424 (upstream operator-registry commit: 85f8c5dbd7e44c27a0e8ba6394da2625aaff3ba2)
f3576e6
Fixes operator-framework/operator-registry#424 Upstream-repository: operator-registry Upstream-commit: 85f8c5dbd7e44c27a0e8ba6394da2625aaff3ba2
0c8f594
Successfully merging a pull request may close this issue.
Is there any need for the configmap-operator-registry scratch image to run as root?
https://github.com/operator-framework/operator-registry/blob/master/configmap-registry.Dockerfile
Can we add this to the image?
The text was updated successfully, but these errors were encountered: