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

Docker build in kompose convert #691

Closed
hrishin opened this issue Jul 10, 2017 · 10 comments
Closed

Docker build in kompose convert #691

hrishin opened this issue Jul 10, 2017 · 10 comments

Comments

@hrishin
Copy link

hrishin commented Jul 10, 2017

kompose convert provides nice utility for converting docker-compose resources to kubenetes resources. However while leveraging on it if compose file has build: tag, so converting those resources to kubernates resources wont help much in our case as another system expects docker image do exists in respective registry prior bringing kubenetes deployment up and running.
It would be great if we can add optional flag in kompose convert -bso on presence of it kompose can build docker images, push it to respective registry and the execute conversation process as a whole.

As of now I can see this functionality is available in kompose up command but we don't want to spin up the pods/containers.

@hrishin hrishin changed the title Docker build in converter Docker build in kompose convert Jul 10, 2017
@surajnarwade
Copy link
Contributor

@hrishin , try this kompose convert --build=local, I forgot to mention it earlier, sorry about that

@cdrage
Copy link
Member

cdrage commented Jul 10, 2017

Hi @hrishin !

Feel free to view the discussion here: #521 on why build/push wasn't added to convert 👍

@surajnarwade
Copy link
Contributor

@cdrage , but I can see --build flag as well when I do kompose convert -h

@cdrage
Copy link
Member

cdrage commented Jul 10, 2017

@surajnarwade Woops, let me clarify, As to why build/push wasn't enabled by default when added to convert 👍

@hrishin
Copy link
Author

hrishin commented Jul 14, 2017

@cdrage @surajnarwade
Thanks!

So are we going to release this feature in next release?

@cdrage
Copy link
Member

cdrage commented Jul 14, 2017

@hrishin Yup! We just graduated (hence why we're in Kubernetes land now) and haven't made the announcement yet, but we will be coinciding the graduation blog post with a 1.0.0 release!

@surajnarwade
Copy link
Contributor

@cdrage @hrishin i think we can close this issue

@cdrage
Copy link
Member

cdrage commented Jul 19, 2017

@surajnarwade Once 1.0.0 is out the issue is solved and we can close this.

@surajssd
Copy link
Member

@hrishin can you verify with the latest release that your issue is solved?

@hrishin
Copy link
Author

hrishin commented Jul 24, 2017

Yes its resolved now, thanks! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants