build failed: kaniko:executor latest doesn't work

[dcaud]

My cr_deploy_plumber was working, but now there's an auth error.

Changing from:

gcr.io/kaniko-project/executor:latest

to

gcr.io/kaniko-project/executor:v1.6.0

using trace(googleCloudRunner::cr_buildstep_docker, edit=TRUE) resolved the problem

I presume this is a bug with google, so it isn't likely needed for a permant fix

See https://github.com/GoogleContainerTools/kaniko/issues/1791

[simitpatel]

thank you @dcaud ! this error gave me great grief, started half-wondering if i needed to re-architect my whole process because of this....thank you so much for the fix!

[MarkEdmondson1234]

Thanks, yes looks like a bug that will be fixed, but fixing the version as you did to to :v1.6.0 is part of why Docker is handy. I feel I have to leave it on :latest within the package and rely on reports like this though, else I'd need some constant monitoring of images.

[MarkEdmondson1234]

One note on fixing it, the cr_deploy_*() functions are all higher order that wrap cr_buildstep() so you could also examine the cloud build yaml created and modify that directly.

[MarkEdmondson1234]

I"m guessing this was temporary and it fixed itself?

[MarkEdmondson1234]

Its not fixed, still an issue - changing to this version solves it though https://github.com/GoogleContainerTools/kaniko/issues/1604

gcr.io/kaniko-project/executor:v1.6.0-debug

It seems to only affect if you push to a different project than the CLoud Build is executing in?

[MarkEdmondson1234]

I guess the fix is in v1.7.0 but there is a bug where its pulling 1.6.0 instead? https://github.com/GoogleContainerTools/kaniko/issues/1822