-
Notifications
You must be signed in to change notification settings - Fork 8
🧹 Migrate to buildah action for building multi-arch images #270
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
🧹 Migrate to buildah action for building multi-arch images #270
Conversation
|
Skipping CI for Draft Pull Request. |
5ff402c to
ec694fd
Compare
|
It fails to build kn-event test images for e1: e2: e3: Build log: https://github.com/cardil/kn-plugin-event/actions/runs/3583459982/jobs/6028914644 Worth adding that Another run, with Build log: https://github.com/cardil/kn-plugin-event/actions/runs/3592174658/jobs/6047577917 I think, I'll try to deploy a s390x RHEL vm and try to reproduce on clean system. Those errors might be related to buildah multi-arch builds.... /hold |
|
The errors described in #270 (comment) has been fixed by openshift-knative/hack#11 |
a68d1cd to
d4aeb74
Compare
|
/cc @mgencur |
|
/unhold /cc @dsimansk |
| @@ -0,0 +1,16 @@ | |||
| FROM docker.io/library/golang:1.19 AS builder | |||
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.
Any concerns about hitting docker.io pull limits?
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.
Yeah. I've looked at the ubi8/go-toolset image before, but it doesn't have the Go 1.19 yet.
The lag of those Go version made us to switch using the OpenShift CI builder image instead, but that image would require authentication...
The auth is also required for ubi8/go-toolset image...
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.
We may use quay.io/projectquay/golang, which says it tracks docker.io/library/golang, but it doesn't have s390x variant... 😿
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 for the explanation. IMO it's fine for now. We probably don't produce enough builds to hit it.
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.
/hold
Let's see productization team opinion...
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.
@dsimansk: Thanks for the explanation. IMO it's fine for now. We probably don't produce enough builds to hit it.
Well, that depends on how the Docker.com counts, right? We will be executing this on Github's infra, so other OSS projects could influence us.
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.
/unhold
The productization team needs time to answer, if we can use any other multi-arch image for Github actions (preferably without auth).
| push: | ||
| branches: ['release-*'] | ||
| branches-ignore: | ||
| - 'main' |
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.
Should the ignore include ci/* branches?
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.
I'd probably just keep branches: ['release-*'] rather then switch to opposite variant.
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.
Done in a454a89
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.
That change is with openshift-knative/hack#12
Both would allow running this workflow on push to some development branch on fork (without pushing to registry thanks to openshift-knative/hack#12)
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cardil, dsimansk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherrypick release-1.8 |
|
@cardil: new pull request created: #284 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Changes