- Notifications
You must be signed in to change notification settings - Fork87
fix: go back to using root user in Dockerfile#600
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
We have to do this because we have no active way to changepermissions to $GITHUB_OUTPUT to a specific user whenrunning the containerAdd trivy ignore to top of Dockerfile to pass lintingSigned-off-by: jmeridth <jmeridth@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Pull Request Overview
This PR reverts the Dockerfile back to using the root user instead of a non-root user due to permission issues with writing to$GITHUB_OUTPUT when running in a container environment. The change removes the user creation and switching logic while adding a trivy security scanner ignore directive.
- Removes non-root user creation and switching to resolve GitHub Actions output permission issues
- Adds trivy ignore directive to suppress security warnings about running as root
- Simplifies the Dockerfile by removing user management complexity
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
c2ad23c intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Fixes#598
Pull Request
Proposed Changes
We have to do this because we have no active way to change permissions to $GITHUB_OUTPUT to a specific user when running the container
Add trivy ignore to top of Dockerfile to pass linting
Readiness Checklist
Author/Contributor
make lintand fix any issues that you have introducedmake testand ensure you have test coverage for the lines you are introducing@jeffrey-luszczReviewer
fix,documentation,enhancement,infrastructure,maintenance, orbreaking