-
Notifications
You must be signed in to change notification settings - Fork 321
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
Publish Multi Arch images #1716
Publish Multi Arch images #1716
Conversation
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
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.
Greaaaaat! Just leave a minor comment. By the way, would you mind adding some instructions in DEVELOPMENT.md about how to build multi-arch images locally? Thanks!
.github/workflows/test-job.yaml
Outdated
docker image tag kuberay/operator:${{ steps.vars.outputs.sha_short }} quay.io/kuberay/operator:nightly; | ||
docker push quay.io/kuberay/operator:nightly | ||
if: contains(fromJson('["refs/heads/master"]'), github.ref) | ||
CGO_ENABLED=1 GOOS=linux GOARCH=$GOARCH go build -tags strictfipsruntime -a -o manager-$GOARCH main.go |
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.
nit: Why do we use CGO_ENABLED=1
instead of CGO_ENABLED=$CGO_ENABLED
?
context: ${{env.working-directory}} | ||
file: ${{env.working-directory}}/Dockerfile.buildx | ||
push: ${{env.PUSH}} | ||
provenance: false |
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.
Note: #1630 (comment)
9c473f2
to
0ddc132
Compare
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.
Thanks! Let's merge it and check whether it publishes the multi-arch images successfully or not.
Why are these changes needed?
See #1630
Related issue number
Closes #1630
Checks