-
Notifications
You must be signed in to change notification settings - Fork 5
Security fixes #504
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
Security fixes #504
Conversation
tlogan2000
left a comment
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.
LGTM assuming you can fix the docker build failure
tlvu
left a comment
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.
LGTM, please take a look at my comments.
|
Just to speed up this PR, as long as the github build works, you can merge this PR. If write permission error when added to PAVICS stack, we can fix in a separate PR. |
Overview
This PR adds a few security recommendations. The SBOM and provenance adjustment is for testing purposes as the GitHub Workflow doesn't currently push to DockerHub, but once we no longer have Docker autobuild services, we may be using this for production.
Changes:
setuptoolsto address a CWE issuenodefaultssource in conda configurationsnonrootuser for running the Docker serviceRelated Issue / Discussion
Docker Teams Pro subscription is ending in a few weeks. Birdhouse docker images will need to migrate to using the
pushoption indocker/build-push-actionvery soon.