Kaniko task failing with removing certs

[raffamendes]

Hi guys, I'm trying to use kaniko task to build a container image in a pipeline, and I'm getting this error

STEP-BUILD-AND-PUSH

E0727 14:26:02.761425      14 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
    For verbose messaging see aws.Config.CredentialsChainVerboseErrors
INFO[0006] Resolved base name quay.io/quarkus/ubi-quarkus-native-image:21.1.0-java11 to build 
INFO[0006] Using dockerignore file: /workspace/source/quarkus-camel-tz-converter/.dockerignore 
INFO[0006] Retrieving image manifest quay.io/quarkus/ubi-quarkus-native-image:21.1.0-java11 
INFO[0006] Retrieving image quay.io/quarkus/ubi-quarkus-native-image:21.1.0-java11 from registry quay.io 
INFO[0007] Retrieving image manifest registry.access.redhat.com/ubi8/ubi-minimal:8.4 
INFO[0007] Retrieving image registry.access.redhat.com/ubi8/ubi-minimal:8.4 from registry registry.access.redhat.com 
INFO[0007] Built cross stage deps: map[0:[/project/target/*-runner]] 
INFO[0007] Retrieving image manifest quay.io/quarkus/ubi-quarkus-native-image:21.1.0-java11 
INFO[0007] Returning cached image manifest              
INFO[0007] Executing 0 build triggers                   
INFO[0007] Unpacking rootfs as cmd COPY pom.xml /project/ requires it. 
error building image: error building stage: failed to get filesystem from image: error removing ./etc/ssl/certs to make way for new symlink: unlinkat /etc/ssl/certs/ca-bundle.crt: device or resource busy

Expected Behavior

Kaniko Task building and pushing my image into openshift internal registry

Actual Behavior

Kaniko task fails

Steps to Reproduce the Problem

1. Create a simple pipeline and try to execute the kaniko task with a COPY command

Additional Info

I actually found this issue in the kaniko github https://github.com/GoogleContainerTools/kaniko/issues/1692 and I'd like to check on this side if there's a solution or you guys think this issue is caused by tekton actually,

Regards.

[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](https://github.com/tektoncd/catalog/issues/796#issuecomment-1000924541): >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](https://github.com/tektoncd/plumbing). Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.