-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 "no-cache" in the buildkit based builds #3834
Conversation
We now build three images using buildkit. The first one is successful, but the 2nd one fails with 401. I'm not sure why exactly, but the only way to make that work is to pass the `--no-cache` flag, which appartently forces buildkit to obtain a fresh auth token. Signed-off-by: Andrea Frittoli <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
Interesting, thanks for fixing this @afrittoli ! |
/test pull-tekton-pipeline-integration-tests |
/test pull-tekton-pipeline-build-tests |
Cool and Thank you, Andrea! :) |
/lgtm Let's get this in and a nightly kicked off! |
Changes
We now build three images using buildkit. The first one is
successful, but the 2nd one fails with 401.
I'm not sure why exactly, but the only way to make that work
is to pass the
--no-cache
flag, which appartently forcesbuildkit to obtain a fresh auth token.
Signed-off-by: Andrea Frittoli [email protected]
/kind misc
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes