Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docker swarm mode] The traefik.docker.network seems to have no effect #719

Closed
vincentlepot opened this issue Oct 6, 2016 · 6 comments
Closed
Assignees
Labels
area/provider/docker kind/bug/confirmed a confirmed bug (reproducible).
Milestone

Comments

@vincentlepot
Copy link

When a service is linked to 2 networks (say network1 and network2), and traefik service is linked to one of the network (say network1), it seems to try to use the other one (I suppose it's a 50% probability)

I tried to set the label traefik.docker.network=network1 on the service, but it seems to have no effect.

This has been tried with the traefik:camembert tag container.

@vincentlepot
Copy link
Author

FYI and to help you test, switching the order of the --network in the service creation command makes Traefik use the other network...

@vdemeester vdemeester added the bug label Oct 7, 2016
@vdemeester
Copy link
Contributor

@vincentlepot it's a little tricky 😄. Without the traefik.docker.network label, it doesn't know which one to use so I guess it gets the first one (maybe 50/50 chance but not even sure.). And as traefik doesn't know (yet 👼) on which network it is, it cannot choose the right one.

Marking as a bug though as it should handle the traefik.docker.network label… I'll take a look at it 😉

@vdemeester vdemeester self-assigned this Oct 7, 2016
@vdemeester vdemeester added this to the 1.1 milestone Oct 7, 2016
@vincentlepot
Copy link
Author

Found the bug, I push a PR

@Id2ndR
Copy link

Id2ndR commented Jun 14, 2017

I still encounter the problem in current traefik version. I'm not using swarm mode. I have:

  • create traefik network
  • traefik in it own compose project, using traefik external network
  • nextcould in it compose project, using traefik external network and default project network

After recreating containers lots of time, I've seen that:

  • sometime traefik register the nextcould IP of default project network, and then a gateway timeout when trying to access trought traefik
  • sometime traefik register the nextcould IP of traefik network, and then access trought traefik is OK

@nmengin
Copy link
Contributor

nmengin commented Jun 14, 2017

@Id2ndR Thanks for your interest in Traefik !

Every question in the issues means features less 😉.

The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, refer to one of the following:

@Id2ndR
Copy link

Id2ndR commented Jun 14, 2017

@nmengin In fact I was thinking it was an issue, because of the apparently random behavior of træfik. It seems to match the description of @vincentlepot and maybe the bug still is present whereas it was closed after PR.
I will copy my comment in Stack Overflow.

@traefik traefik locked and limited conversation to collaborators Jun 14, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/provider/docker kind/bug/confirmed a confirmed bug (reproducible).
Projects
None yet
Development

No branches or pull requests

5 participants