Skip to content

Conversation

baptistedonaux
Copy link
Contributor

Initial template works with current model network.

If you use the new overlay network (ex. docker-compose --x-networking up), the golang structure RuntimeContainer -> []Address doesn't contain IP (empty string).

Use []Network array resolved the problem.

@jwilder
Copy link
Collaborator

jwilder commented Jan 15, 2016

This file is just an example. Were you intending to fix this issue w/ nginx-proxy?

@baptistedonaux
Copy link
Contributor Author

I send PR on jwilder/nginx-proxy.

But I think that fix template example right now will limit the feedback, because the new model network will be activate systematically in the docker-compose next release. For docker-compose 1.6, the containers IP will be set in []Network and not more in []Address.

jwilder added a commit that referenced this pull request Jan 26, 2016
Deal with networks (supports new overlay network)
@jwilder jwilder merged commit 9bfce75 into nginx-proxy:master Jan 26, 2016
@jwilder
Copy link
Collaborator

jwilder commented Jan 26, 2016

Thanks @baptistedonaux!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants