Docker links deprecated, what will happen to the discovery service?

[Fabio Lorenzi]

Given that the --link docker run option is going to be deprecated how would a docker discovery bridge work?

[clement escoffier]

Hello,

The bridge parses the environment variables. So if the environment variables uses the same "structure" it will continue to work. Links are not deprecated when using docker-compose, so this will continue to work. 

I didn't look how user-defined network (which is the replacement for links) can be used with service discovery. I believe it won't as in a user-defined network you define the name of each service (so you don't need discovery). 

Clement

[Fabio Lorenzi]

Hi Clement.

I'll definitely use links for the foreseeable future.

Just for the sake of discussion...

I see what you are saying. But defining a name for a service doesn't automatically give you the port to connect to so how could you eventually contact your vertx rest service `b` in container B from verticle `a` in container A just knowing that they share a network? It looks similar to the --link scenario so I would expect some kind of discovery needed. Am i getting something wrong?

Anyway... I'll give a shot to some alternatives and eventually come up with a bridge of sort :D