Can I ask why it is not in plans? I assume it would be very useful to do so.

Can you elaborate on the why? And on the alternatives (if they exist)?

depends_on is a no-op when used with docker stack deploy. Swarm mode services are restarted when they fail, so there's no reason to delay their startup. Even if they fail a few times, they will eventually recover.

@brettmc

So what is the supported depends_on syntax for v3?

When using docker-compose, the supported syntax for v3 is the list syntax (similar to the one used for 2.0). If you're using docker stack deploy, dependencies will not be honored (see above for justification)

The version 3 format is the first step in moving away from the external docker-compose tool towards the integrated docker stack solution. The current implementation has its quirks which are being worked on. Support for the version 3 format in docker-compose is meant to help that transition. A lot of things have changed and improved in Docker since fig / Compose was first introduced, and that means a lot of the things that used to make sense have now become obsolete. docker stack is a fresh start using new concepts and sheds away some of the more unwieldy syntax and concepts, from volumes_from to depends_on.
If you have particular concerns about some of those changes, please report them over on the docker/docker repo where it is being actively iterated on.
If you are not yet ready to transition to Docker services and docker stack, feel free to keep using the v2 format. While it's reasonable to assume the project will be sunset at some point in the future, it will be announced well in advance. And after that the code will remain available and open source.

Depends_on in version3 #4305

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions