Open rikirolly opened 2 years ago
I discovered the problem is not related to git pull but probably to the information contained in my repository. Still don't know where the problem reside.
Probably e problem in go-git module: https://github.com/go-git/go-git/pull/111
It seems the issue you referenced was fixed in the go-git PR here: https://github.com/go-git/go-git/pull/392
kaniko adopted go-git w/ the fix PR in it in the PR here - https://github.com/GoogleContainerTools/kaniko/pull/1885 (Jan 2022)
which should have been in the v1.8.0
release in March 2022. As such I think the kaniko version you used already had the go-git fix for the issue you referenced
Perhaps there is some other issue? Are you still encountering this issue?
I am facing the same issue with kaniko executor 1.9.1. Still not finding any solution
Was not able to find a way to handle this, so used a workaround: archive and push source code to s3 bucket, use s3 as context. Stupid, but works smoothly.
Does someone successfully configured kaniko with AWS Codecommit?
I failed trying in this way:
This is the error: