-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to multi-tag #217
Comments
Hey @LeDominik, you can pass in multiple destinations to push the image too by setting the |
Oh cool, I didn't even try because for the build parameters it was clearly outlined in the help text 👍 |
@priyawadhwa I've tried to use multiple |
Hey @saschak094 I rebuilt the executor image and this should work now. |
Hey @priyawadhwa just tried it with the newest image but we are still not able to push to multiple destinations |
Hey @saschak094 , thanks for letting me know! I just changed how we release the executor image, so hopefully shouldn't face this problem again. Could you try again with the new :latest image? |
Hey @priyawadhwa, |
Hello, I'm using kaniko in a GitLab CI Pipeline, which works fine with one tag, but with two destination flags I only get the tag of the last destination flag in the registry. Is something wrong with my command?:
EDIT Sorry, it works, it was my fault: I've forgotten to tag the commits on my test-branch, so |
Hey @d-sko what version of kaniko are you using? |
Hi guys, I have same situation, on multiple destinations, only last one is reaching repository. We use gcr.io/kaniko-project/executor:debug image. |
@giulio1979 - did you anywhere when trying to set multiple destinations with the |
@callumd789 it is working for me, see https://gitlab.com/alinex/docker-mkdocs/blob/master/.gitlab-ci.yml |
The flag is mostly self-explanatory, but its usage for multiple push was not documented anywhere. Related to GoogleContainerTools#217, GoogleContainerTools#733
The flag is mostly self-explanatory, but its usage for multiple push was not documented anywhere. Related to GoogleContainerTools#217, GoogleContainerTools#733 Co-authored-by: Nils Van Zuijlen <nils.van-zuijlen@mailo.com>
The flag is mostly self-explanatory, but its usage for multiple push was not documented anywhere. Related to GoogleContainerTools#217, GoogleContainerTools#733 Co-authored-by Nils, submitted to the public domain. Nils Van Zuijlen <nils.van-zuijlen@mailo.com> See: GoogleContainerTools#3042
The flag is mostly self-explanatory, but its usage for multiple push was not documented anywhere. Related to GoogleContainerTools#217, GoogleContainerTools#733 Co-authored-by Nils, submitted to the public domain. Nils Van Zuijlen <nils.van-zuijlen@mailo.com> See: GoogleContainerTools#3042
In our build-pipeline we always add 2 tags: One for the git hash and one with the branch and or tag for releases, etc... So for
docker build
we simply pass two tags and then push both.I'm wondering if there's a way to support this model in Kaniko as well...BTW awesome tool!
The text was updated successfully, but these errors were encountered: