build
build copied to clipboard
Cannot push to gcr.io with recent kaniko executor > 0.1.0
Expected Behavior
Our build currently depends on a recent kaniko executor. It may be possible to use the 0.1.0, but we are seeing errors resolving build args that "just work" with later releases. This issue did not present itself until we tried to push to gcr.io instead of dockerhub. I would expect that we could push regardless of registry as long as the creds are valid.
Actual Behavior
Get an access denied message when pushing to gcr.io.
Steps to Reproduce the Problem
Simple script is attached to repro the issue.
That script should fail. If the executor image in build-bug.yaml is changed to v0.1.0, it works. Also if docker credentials are substituted in and the destination is dockerhub, it works as well (even with the latest executor).
Additional Info
This could very well be a kaniko issue not a knative issue.
/cc @priyawadhwa in case this sounds familiar as a kaniko bug
I'm not familiar with this bug 😞 @berndtj would you mind opening an issue in the kaniko repo? With some more info we should be able to figure out if it's a bug in kaniko.
Sure, will do
https://github.com/GoogleContainerTools/kaniko/issues/392
This was fixed with https://github.com/knative/build-templates/pull/87