-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Warmer behaviour changed in the 1.12.0 release breaking pipelines #2602
Comments
Potentially coming from this new feature:
|
Thanks you for flagging this @RoSk0, this is due to a bug in PR #2499 in which the Dockerfile path is always validated even when the flag is not supplied (it will always break for regular/previous |
I have bumped all named tags back to v1.11.0 for kaniko's released images. This includes:
|
|
We are using
gcr.io/kaniko-project/executor:debug
to get latest features of the Kaniko so spotted this quite quickly.To avoid building image for the same commit twice, we use this technique:
Actual behavior
The output is full, but redacted:
Expected behavior
Yesterday, and many many days before, the build was successful with this output:
To Reproduce
Steps to reproduce the behavior:
Additional Information
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: