docker-compose build --push <registry>

[cy8aer]

This would be a nice feature for creating and deploying of containers on a different (development) machine than the productive ones (which may run via image: option)

[dnephin]

Some related issues #213, #457

[jmmills]

I would give this a +1 as either an addition to docker-compose or as part of a different "build tool".
In addition it would be nice (and UNIXy) to add an "images" verb, so as to output a flat list of the images built by the tool.
I'm thinking things like this would be possible:

$ docker-compose build
$ docker-compose images | while read i; do docker save $i -o $i.tgz ; done

Thoughts?

[Addendum] Additionally, this would perhaps solve the problem of pushing?

$ docker-compose images | while read i ; do docker push my.registry.server:5000/$i ; done

[PeterRJones]

+1
docker-compose is the best/easiest way to build a bundle of related docker images. Being able to easily push these resulting docker images to a registry is a natural extension of this workflow. My use-case is a development use-case where a bundle of images are built by Jenkins. I'd like to be able to easily push these images somewhere for developers to pull and use/run.

[FelikZ]

👍

[rashtao]

+1

[binaryanomaly]

+1

[arthurbarros]

+1

[crackmac]

+1 (and another +1 for a vote feature in github)

[clemensberndt]

+1

[tgagor]

+1