-
Notifications
You must be signed in to change notification settings - Fork 2.8k
DNM: test staged-layer-creation vendor #27251
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
base: main
Are you sure you want to change the base?
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99 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 |
b60c4a4 to
03789f8
Compare
03789f8 to
b5d82ad
Compare
|
PR needs rebase. 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-sigs/prow repository. |
Signed-off-by: Paul Holzinger <[email protected]>
b5d82ad to
2cdc301
Compare
No idea how this could be related to my changes, I suspect it is a flake and somehow once we get an error with a idmapped pulled image all following commands fail to create the idmapped layer? Seems quite concerning, I am going to press rerun just to be sure. |
|
Ok not a flake I guess, trying to debug why this only fails on debian like that. |
|
So the required step to reproduce this is |
Does this PR introduce a user-facing change?