Interlock is ignoring services with no ports

[groyee]

I must be missing something here but I really don't understand why Interlock doesn't add a new docker containers when it has no exposed ports?

All I am trying to do is to get the IP addresses of containers running with a specific name.

Is that how it suppose to be by design? Why?

Maybe there is some other solution that I am not aware of? How else can I discover the address of my containers in a distributed swarm cluster with an overlay network?

Thanks.

[ehazlett]

What version of Docker are you using?

On Aug 26, 2016 19:42, "Sasha Goldberg" notifications@github.com wrote:

I must be missing something here but I really don't understand why
Interlock doesn't add a new docker containers when it has no exposed ports?

All I am trying to do is to get the IP addresses of containers running
with a specific name.

Is that how it suppose to be by design? Why?

Maybe there is some other solution that I am not aware of? How else can I
discover the address of my containers in a distributes swarm cluster with
an overlay network?

Thanks.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#198, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP6IolmYIh332WVZs1fR5tVgvAwJDynks5qj3nogaJpZM4JujX-
.

[groyee]

1.12

[ehazlett]

Interlock isn't compatible with 1.12 services yet. There is a wip branch
for that. See #186

On Aug 26, 2016 8:55 PM, "Sasha Goldberg" notifications@github.com wrote:

1.12

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#198 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP6Itjke4EaiQ3llFjf-XrwBeAa0zi0ks5qj4sRgaJpZM4JujX-
.

[groyee]

Thanks!