-
Notifications
You must be signed in to change notification settings - Fork 2
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
Quality check for docker image is failing because of root user #353
Comments
i guess you mean this workflow https://github.com/catenax-ng/tx-item-relationship-service/actions/workflows/quality-checks.yaml
will check with our team. |
Hey, |
Hi @ds-psosnowski this is currently a problem we get aware also from https://github.com/catenax-ng/tx-traceability-foss/blob/main/Dockerfile that was referenced in in #341 and we opened a issue against helm helm/helm#12385 itself. but thinking also about rewriting our checks for that. |
@FaGru3n |
@ds-psosnowski , @FaGru3n I think there is a little disconnect here, the issue reported isn't related to the helm one (helm/helm#12385) but to our implementation of the non root user check which is unable to resolve the variable references ${UID}:${GID} in USER, see the comment from @SebastianBezold #341 (comment) . |
moved to our backlog, to plan it properly |
Is your support request related to a problem? Please describe.
One of our quality check is failing -
Failed! Guideline description: Container images shall not run as root for security reasons.
We are not sure if this is not caused by defining user from env variables:
USER ${UID}:${GID}
Or maybe because we didn't specify user for build image.
Describe the solution you'd like
If this is caused by using env variables then check shouldn't fail.
Additional context
Dockerfile for verification: https://github.com/catenax-ng/tx-item-relationship-service/blob/main/Dockerfile
The text was updated successfully, but these errors were encountered: