-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
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
Ensure trivy docker image runs as a non root user #519
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
braudel
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jun 8, 2020
@rahul2393 could you work on it? |
Sure, thanks |
Fixed by #570. Thanks, @rahul2393 |
liamg
pushed a commit
that referenced
this issue
Jun 7, 2022
liamg
pushed a commit
that referenced
this issue
Jun 7, 2022
josedonizetti
pushed a commit
to josedonizetti/trivy
that referenced
this issue
Jun 24, 2022
Hi, this was reverted in #581. Is it likely to be something that another attempt could be made at? I did see there were some issues with the ownership of a cache directory. |
It broke scanning in container images on Windows. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attempts to launch trivy using starboard are currently failing in k8s clusters with PSP restricted due to runAsNonRoot.
The text was updated successfully, but these errors were encountered: