Using Kaniko v1.9.2 executor

[mchutani-CS]

Expected Behavior

The Task should be able to run with the latest Kaniko image: gcr.io/kaniko-project/executor:v1.9.2@sha034f15e6fe235490e64a4173d02d0a41f61382450c314fffed9b8ca96dff66b2

Actual Behavior

Error with running the Task

Status: CouldntGetTask
Logs:

 Warning  Failed         7m34s  TaskRun  failed to create task run pod "build-push-pipeline-run-1xsc5m-build-push": translating TaskSpec to Pod: duplicate unique image found for platform: unknown/unknown: found sha256:36cd9b9af686787a290372e9c7e4d5b27cd02503248d5a289262d6772905a2ec and sha256:a1585c528f713d20b357a3fd7be7e02fad16a3a6efa │
│ 1abece583591f0463addd. Maybe missing or invalid Task default/kaniko

Steps to Reproduce the Problem

1. Fetch the yaml file from here: https://github.com/tektoncd/catalog/blob/main/task/kaniko/0.6/kaniko.yaml#L32
2. Replace Line Add a specific version and context support for kaniko  #32 to: gcr.io/kaniko-project/executor:v1.9.2@sha034f15e6fe235490e64a4173d02d0a41f61382450c314fffed9b8ca96dff66b2
3. Run the task

Additional Info

The reason I'm trying to use the latest is because the default version v1.5.1 is having some security vulnerabilities that I would like to get fixed.

[vdemeester]

There was an issue on the pipeline side (tektoncd/pipeline#6257) that got fixed recently. The fix should be available in 0.47.0.

[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.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.