Skip to content
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

can you specify multiple destinations ? #733

Closed
maurorappa opened this issue Aug 7, 2019 · 10 comments
Closed

can you specify multiple destinations ? #733

maurorappa opened this issue Aug 7, 2019 · 10 comments

Comments

@maurorappa
Copy link

It seems I cannot make kaniko to push an image to multiple places repeating the destination option. is it possible in any way?

@priyawadhwa
Copy link
Collaborator

Hey @maurorappa setting the --destination flag multiple times should work -- could you provide some logs?

@maurorappa
Copy link
Author

my bad, I managed to push to jfrog.io and AWS ECR in one go!
Kaniko rocks!

@marekaf
Copy link

marekaf commented Jan 9, 2020

this doesn't seem to be document well though :(

@gstolz
Copy link

gstolz commented Nov 4, 2020

If multiple pushes to registries are ok, how about a combination of tar-export and push, would that be possible?

@felixdivo
Copy link

Couldn't this be documented in the flags listing in the repo README?

@yuge-dev
Copy link

Adding this to the documentation would be helpful...

@mmurasawa
Copy link

thanks

@sinhasonalkumar
Copy link

my bad, I managed to push to jfrog.io and AWS ECR in one go!
Kaniko rocks!

Can plz share snippet. How did you managed creds for both ecr and jfrog artifactory.

@henricook
Copy link

henricook commented Jan 23, 2024

@priyawadhwa Would you mind adding a definitive comment here please? To push my built image to two places I just need two --destination params, is that right? I've seen other posts saying I might also need --cleanup and it's still not in the docs as far as I can see

My use case is like several others: In some situations when building an image I want to store it against its commit SHA but also push to latest-{branchname}

@henricook
Copy link

henricook commented Jan 23, 2024

In the meantime, for any other readers, this does appear to work for me. The push messages can be a bit confusing because it always outputs a digest in 'pushed', but it is pushing to two places with two --destination tags

INFO[0145] Pushing image to registry.mycorp.com/myproject/project:abcdef
INFO[0148] Pushed registry.mycorp.com/myproject/project@sha256:98c377879e8d8e3d5ccca8b704c5c66fce4bd69095d8b36c7eb155c9e8265be5 
INFO[0149] Pushing image to registry.mycorp.com/myproject/project:latest-main
INFO[0152] Pushed registry.mycorp.com/myproject/project@sha256:98c377879e8d8e3d5ccca8b704c5c66fce4bd69095d8b36c7eb155c9e8265be5 

nils-van-zuijlen added a commit to nils-van-zuijlen/kaniko that referenced this issue Mar 4, 2024
The flag is mostly self-explanatory, but its usage for multiple push
was not documented anywhere.

Related to GoogleContainerTools#217, GoogleContainerTools#733
dchaley pushed a commit to dchaley/kaniko that referenced this issue Aug 2, 2024
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 <[email protected]>
dchaley pushed a commit to dchaley/kaniko that referenced this issue Aug 2, 2024
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 <[email protected]>
See: GoogleContainerTools#3042
dchaley added a commit to dchaley/kaniko that referenced this issue Aug 2, 2024
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 <[email protected]>
See: GoogleContainerTools#3042
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants