update go-containerregistry so that kaniko works with Harbor #227
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! Thanks for maintaining the great project!
Recently, I confirmed current version of kaniko doesn't work well with Harbor as I stated two issues below:
After my research, I understand the reason might be harbor's implementation. However, my workaround(google/go-containerregistry#219) was merged in go-containerregistry to make go-containerregistry more robust on various docker container registry implementations even when some implementations doesn't follow the docker registry specs. Also, another issue(google/go-containerregistry#220) reported that exactly the same error happens in gitlab.
So, I would like kaniko to pull the change so that kaniko works nicely with private docker registry implementations (at least with harbor, gitlab).