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

[vincentlepot]

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]

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

[vdemeester]

@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 😉

[vincentlepot]

Found the bug, I push a PR

[Id2ndR]

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]

@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:

• Stack Overflow using the "traefik" tag
• the Traefik community Slack channel

[Id2ndR]

@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.