Joffrey F

> . I think, docker does not fully support the "username:[email protected]" syntax that you use. That is correct. The correct way to use auth over a private registry is to...

Can I close this or is there anything that's still unclear regarding private registry auth?

When pushing to a private registry over HTTP, do you not get this message? I'll look into adding a note for the HTTPS stuff in our docs. ``` $ docker...

Hi, Sorry – that's not something we support at the time. A patch adding sentinel support would of course be most welcome :)

Hi @samrocketman As far as I can tell, the issue you're reporting is a Docker networking issue, not a Compose issue. If you concur, please open an issue on the...

Hi! I believe that is the expected behavior, yes. The command you're running `docker-compose up [...] web` is explicit about handling the `web` service, and not any other - having...

Hi @mkubilus There are some advanced templating features in the experimental build that you may want to try out. For example, you would be able to write the following `docker-compose.yml`...

Does it happen if you turn off your WiFi? Could be related to https://github.com/docker/docker-py/issues/1076. Another theory, if your service has `tty: True` enabled, could be #3106

Are you looking for [`aliases`](https://docs.docker.com/compose/compose-file/#aliases)?

They're always fully qualified.