Skip to content
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

Use BuildKit's option to not tar the output image as OCI layout as we need it as a directory anyway #1362

Conversation

SaschaSchwarze0
Copy link
Member

Changes

This updates the BuildKit sample build strategy to use the recently introduced tar=false option on the output. This causes the files directly getting written to a directory that I pass in as dest. This saves us the extraction that we so far did.

I am also removing the metadata-file creation. We needed that before shipwright-managed push because we grabbed the digest from it. Now, Shipwright sets it now as part of the push.

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

Release Notes

The BuildKit sample build strategy now does not cause BuildKit to tar the image to then untar it

@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 22, 2023
@openshift-ci openshift-ci bot added release-note Label for when a PR has specified a release note do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Aug 22, 2023
@openshift-ci openshift-ci bot requested review from otaviof and qu1queee August 22, 2023 14:38
@SaschaSchwarze0 SaschaSchwarze0 changed the title WIP Use BuildKit's option to not tar the output image as OCI layout as we need it as a directory anyway Use BuildKit's option to not tar the output image as OCI layout as we need it as a directory anyway Aug 22, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 22, 2023
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.12.0 milestone Aug 22, 2023
@qu1queee qu1queee requested review from coreydaley and removed request for otaviof August 23, 2023 13:05
@coreydaley
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 23, 2023
@SaschaSchwarze0
Copy link
Member Author

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 29, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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

The pull request process is described here

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 29, 2023
@openshift-merge-robot openshift-merge-robot merged commit 6dee001 into shipwright-io:main Aug 29, 2023
@SaschaSchwarze0 SaschaSchwarze0 deleted the sascha-buildkit-no-tar branch August 7, 2024 18:28
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. lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants