-
Notifications
You must be signed in to change notification settings - Fork 113
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
Docker: bump alpine base image to v3.17
#3703
Conversation
Could you also update the alpine version in docker/Dockerfile.revad-eos? |
@vascoguita have you tried running an alpine-built The image built correctly, but there were many static linking issues hard to fix when using alpine rather than the EOS image for the builder step. |
Oh I see, I'll test it and if it fails I'll try with |
@vascoguita I can save you some time if you check #1705 (when I originally used alpine on the builder step) and #1718 (where I restricted the static linking to the |
I've just tested the revad image built from Dockerfile.revad-eos and apparently it's working: https://github.com/vascoguita/reva/actions/runs/4374000858/jobs/7652883570 |
@vascoguita looks promising. I'm not sure to which extent these tests check all the services in reva and how they interact with the eos binary but this might be reviewed in the future if issues arise. I'll rebase and include it as well on the |
373462d
to
512682f
Compare
Prevents the following CVEs as reported in ArtifactHub: https://artifacthub.io/packages/helm/cs3org/revad?modal=security-report