What is `docker-compose push` supposed to do?

[AndreKR]

I am running docker-compose version 1.9.0, build 2585387 and in the inline help there is an option "push - Push service images".

The lead me to think I could have a service defined in my docker-compose.yml that has build: and image: set. Then I could run docker-compose build and it would build the image locally and tag it with the registry and name I specified. Then I could run docker-compose push or docker-compose push web (for a single service) to push that service's freshly built image to my registry.

In reality, yes, I can build the image with docker-compose build and it is correctly tagged. I could then manually push it with docker push to my registry if I know the image tag. However, docker-compose push does nothing. It doesn't give any error, it just exits successfully after about one second but nothing arrives at the registry. Same when I specify a service name: docker-compose push web

Is docker-compose push meant for something else?

[shin-]

Hi @AndreKR ,

Yes - docker-compose push is specifically a command designed to be used in the context of application bundles. I understand this can be a bit misleading.

[romanlevin]

@shin- Are there plans to rename the command, or clarify the output of docker-compose push --help, or mention something in the documentation?

If not, would you accept a push request for that?

[danabrey]

push request

:)

[Headcult]

Same question here. What does docker-compose push do? It does nothing as of now. Or do we need to use docker-compose bundle --push-images to push our images to Docker Hub? Can we some clarity over this as the Official Docker documentation is not providing enough information.

[mkunissery]

the documentation for docker-compose push is pretty naive. It does let you know any details on whether you can push multiple services using comma seperated names or however.. it has been a year since the last comment which asked for more documentation and nothing in place yet... appropriate support is the key

[jerrygreen]

Agree. It's a weird command, with poorly documented --help & doc on website, it has weird arguments, you may not be sure what it expects

Though, if you know what it is and how to use it, everything is ok

1. If you'll use docker push not_a_service_name, you'll get error "No such service" - at least it prints error, but the message is misleading
2. If you'll use docker push actual_service_name it will do nothing, no error - weird
3. If you'll use docker push your.registry.com/your-service-name, then it'll work as expected

[braytonstafford]

I'm using docker-compose build to build all of my docker images and then using docker-compose push to then push all of those images to their repositories. The documentation may not be long but it does state

Pushes images for services.

Thats what its doing for me right now.

[MartinMuzatko]

I was also a little confused by the documentation. But it does what I expected. docker-compose push even tags the images accordingly. so less work than the manual docker tag work.

[costa]

@braytonstafford I wonder what you have done to make it work for you. For me, and for most people on this page, it does nothing (while docker push works in the same env) — with just a docker-compose.yml and image: within.

[MartinMuzatko]

@costa what docker/docker-compose version are you running?

[costa]

I've upgraded to the latest (1.22) before posting this, of course. Also, `--verbose` didn't reveal anything of interest.

[costa]

@shin- reopen please

[shin-]

#4283 (comment)