JeromeJu

Looks like this cannot be reproduced at HEAD for kaniko v1.20.x where the directories users are also non-root. ``` jeromeju@jju:~/kaniko/workspace$ ./run_in_docker.sh /dockerfile /usr/local/google/home/jeromeju/kaniko gcr.io/jju-dev/test:latest INFO[0000] Using dockerignore file: /workspace/.dockerignore INFO[0000]...

Looking into this, it seems that with the latest image >v1.15.0, the output is: ``` INFO[0004] Saving file . for later use error building image: could not save file: copying...

Verified with v1.9.0 when this bug was filed. The error message was `write /kaniko/0/dev/full: no space left on device` instead of the recursive name that leads to filename too long....

/remove-lifecycle stale #5579 unblocks this

verified that this could be closed.

> @JeromeJu this seems to be stalled waiting for approval for workflows. Is that something you can help with? Thanks @KerchumA222 for the changes, I have re-runned the integration tests...

Thanks to the offline discussion with @aaron-prindle . The pointer led to the design of Kaniko with UID for historical reasons. From Kaniko's previous design, we do not have user...

/ok-to-test

Thanks for submitting this @Rollson . The error comes from [resolveSourceContext](https://github.com/GoogleContainerTools/kaniko/blob/main/cmd/executor/cmd/root.go#L398-L433). It might be helpful if you could help check the subpath of $context and its access?

Could we check if `--context="${{ github.repositoryUrl }}#${{ github.ref }}#${{ github.sha }}"` is set correctly? If so, is this pointing to the correct [context](https://github.com/GoogleContainerTools/kaniko?tab=readme-ov-file#kaniko-build-contexts)?