Closed RoSk0 closed 1 year ago
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 --image
only usage IIUC as it is in v1.12.0
). I am going to push all of the :latest tags back to v1.11.0 and release a v1.12.1 hotfix addressing this issue. I will update this thread when this is done
I have bumped all named tags back to v1.11.0 for kaniko's released images. This includes:
executor
latest -> v1.11.0
debug -> debug-v1.11.0
slim -> slim-v1.11.0
warmer
latest -> v1.11.0
v1.12.1
released now with the fix for this
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
Kaniko Image - Digest: sha256:127b233d0ee0ebde6c4c678b129e8ed7b4655678b212e5c7da2d9738ab6b6e49
Triage Notes for the Maintainers
--cache
flag