Using a Git context, kaniko will fail if the repository already exits in the local filesystem.

[rkamradt]

Actual behavior
My use-case is I'm using Kaniko in Kubernetes to pull source from GitHub, build an image and push to a local repository. My Jenkins pipeline creates a Kaniko pod and will keep it around for a specified amount of time and reuse it if needed. When it gets reused to build from the same git repository if gives the error 'Error: error resolving source context: repository already exists'

Expected behavior
For a git context, it should ignore any exiting files and overwrite them with a new clone, or a pull from the repository.

Additional Information
The repository I am using is here https://github.com/rkamradt/HelloK8sBuild
In particular, the Jenkinsfile creates the kaniko pod to be used to build images.

Triage Notes for the Maintainers

Description	Yes/No
Please check if this a new feature you are proposing
Please check if the build works in docker but not in kaniko
Please check if this error is seen when you use --cache flag
Please check if your dockerfile is a multistage dockerfile

[tejal29]

Thanks @rkamradt for your issue. When we designed kaniko we did not think of it as a pod which could be reusable.
Do you see any performance improvement for your Jenkins job when keeping the pod around and re-using it?

Looking forward to make Kaniko as re-usable as possible.

[rkamradt]

it takes about 30 seconds to spin up a slave pod for kaniko. My workaround, for now, is to create two worker pods, since my pipeline creates an app image and a tester image. You can read more about what I'm trying to accomplish here: https://medium.com/better-programming/playing-with-pipelines-b5cf357ddd06?source=friends_link&sk=fa2e5729c6c8b02641cee94e8b99d340