Connect to network according to network priorities

[ndeloof]

This is a follow-up for docker/cli#1372

see https://gist.github.com/jfellus/cfee9efc1e8e1baf9d15314f16a46eca for a reproduction scenario

[ndeloof]

I was able to confirm we run NetworkConnect in order according to network priorities, but still eth0 is always connected to the first network by lexical order. It seems the actual binding takes place on ContainerStart, need more investigations.

created https://docker.atlassian.net/browse/IL-255 to track this issue internally

[nospam2000]

what is the reason for closing the issue? Has it been fixed? Any reference for tracking in which version it has been fixed?

[ndeloof]

sorry, my bad (was too fast doing issue triage and transfert)

[thediveo]

Any new findings? This is a bug affecting especially container workload developers working with, say, industrial protocols that need direct layer 2 access and it's easy to mess the vNIC ordering up, even when developers clearly spelt-out their deployment requirements in compose v2 using network attachment priorities.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nospam2000]

keep issue open unless resolved

[stale]

This issue has been automatically marked as not stale anymore due to the recent activity.

[vinsgithub]

this bug seems to be still present in compose v3!
Please keep issue open (hopefully solve this :-/ )

[thediveo]

this is a mess, as the priorities also get used in sorting endpoint lists for resolving service names in the embedded DNS resolver.