Skip to content

[release-v0.13] Use buildah instead of docker, support multi-arch builds#215

Merged
kubevirt-bot merged 5 commits intokubevirt:release-v0.13from
kubevirt-bot:cherry-pick-115-to-release-v0.13
Jun 16, 2023
Merged

[release-v0.13] Use buildah instead of docker, support multi-arch builds#215
kubevirt-bot merged 5 commits intokubevirt:release-v0.13from
kubevirt-bot:cherry-pick-115-to-release-v0.13

Conversation

@kubevirt-bot
Copy link
Copy Markdown

This is an automated cherry-pick of #115

/assign awels

Use buildah and podman, enable building multi-arch manifests

maya-r added 5 commits June 16, 2023 19:44
This passes them to all subprocesses, but they can still be overridden
due to the ?= construct.

Signed-off-by: Maya Rashish <mrashish@redhat.com>
Avoid failure when the binary is built with Fedora 36 and thus
requires newer glibc symbols than the container.

Signed-off-by: Maya Rashish <mrashish@redhat.com>
Now we can run:
make clean && \
GOARCH=arm64 make manifest && GOARCH=amd64 make manifest && \
make manifest-push

And spit out a manifest for both arm64 and amd64, in the same image.

Caveats:
- We have a special 'manifest-clean' target, as we can add arbitrarily
  many images to a manifest and don't want the old ones.
  Delete old image in case a regular non-manifest image exists by the
  same name, too.
- The push and image/manifest creation are split, so we can run the
  image creation for more than one architecture and push the combined
  manifest including both.
- We keep `make push` behaving the same to avoid breaking CI.
- Full DOCKER_REPO name is used, as podman-like tools have odd behavior
  with short names.

Signed-off-by: Maya Rashish <mrashish@redhat.com>
Signed-off-by: Maya Rashish <mrashish@redhat.com>
Add a message about this, too

Signed-off-by: Maya Rashish <mrashish@redhat.com>
@kubevirt-bot kubevirt-bot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Jun 16, 2023
@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Jun 16, 2023
@kubevirt-bot kubevirt-bot requested review from awels and maya-r June 16, 2023 19:44
@awels
Copy link
Copy Markdown
Member

awels commented Jun 16, 2023

/lgtm
/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2023
@kubevirt-bot
Copy link
Copy Markdown
Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 16, 2023
@awels
Copy link
Copy Markdown
Member

awels commented Jun 16, 2023

/override pull-hostpath-provisioner-k8s-e2e-storage

@kubevirt-bot
Copy link
Copy Markdown
Author

@awels: Overrode contexts on behalf of awels: pull-hostpath-provisioner-k8s-e2e-storage

Details

In response to this:

/override pull-hostpath-provisioner-k8s-e2e-storage

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.

@kubevirt-bot kubevirt-bot merged commit 8493fc6 into kubevirt:release-v0.13 Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants