Kaniko authentication errors since 0.24 because of HOME env missing

[wwu-cx]

Took me a while to figure this out, i know this is not per se a bug in tekton, but since a lot of people are using the kaniko build step from the library, i will report this.

Expected Behavior

After upgrading to 0.24, the kaniko buildstep should function as before.

Actual Behavior

PUTs to the registry (Useragent kaniko/1.5.2) are working like before, but i see GET and HEAD requests seconds after that are failing with auth problems (401):

192.168.1.99 - - [12/May/2021:13:50:43 +0000] "PUT /v2/kaniko-cache/xyz/manifests/... HTTP/1.1" 201 0 "" "kaniko/v1.5.2"
192.168.1.99 - - [12/May/2021:13:50:51 +0000] "GET /v2/ HTTP/1.1" 401 87 "" "kaniko/v1.5.2"
192.168.1.99 - - [12/May/2021:13:50:51 +0000] "HEAD /v2/kaniko-cache/xyz/blobs/sha256:... HTTP/1.1" 401 167 "" "kaniko/v1.5.2"

after that the step fails with
error pushing image: failed to push to destination ... unexpected status code 401 Unauthorized

what i found out is that since HOME is not set, the .docker/config.json is now created in the /root directory,
in v0.23, it was created unter /home/tekton.

i suppose that there is a problem with how kaniko finds docker/config.json

i updated DOCKER_CONFIG to point to the /root dir, but that didn't help.

what solved the auth problems was to set HOME to /home/tekton like before

Additional Info

• Tekton Pipeline version: v0.24

[vdemeester]

We should update the catalog kaniko task to do that then I think.
/cc @tektoncd/catalog-maintainers

[chmouel]

or contact the kaniko maintainer to set a WORKDIR in the Dockerfile :)

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[ghost]

/assign

[ghost]

/remove-lifecycle rotten

[lbernick]

/priority important-longterm

[dibyom]

/cc @tektoncd/catalog-maintainers is this still an issue?

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[vinamra28]

/remove-lifecycle rotten
/lifecycle frozen