The ability to select the default docker network route and configure network route priority
Tell us about your request A clear and concise description of what you want to happen or the change you would like to see
It would be nice to be able to set the default docker route to a docker network name defined in the compose and define the route priority in either a dictionary or list where the order in the yaml is the order docker would use.
Which service(s) is this request for? Let us know which product(s) you want this for?
Docker compose I think and maybe more under the hood I am not sure.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
There's no way currently to set the default route in docker or to set the priority it uses. Rather the default route and priority is currently selected based on the alphabet of the network name. That makes for a bad user experience and a lot of confusion when using docker networks.
Are you currently working around the issue? A clear and concise description of any alternative solutions or features you've considered or are using today.
My work around is to create networks but append an alphabet letter a-example-network for example so that network is the default network for example and subsequent networks would come after a.
Additional context Add any other context or screenshots about the feature request here.
There's no way currently to set the default route in docker or to set the priority it uses. Rather the default route and priority is currently selected based on the alphabet of the network name.
Real ????????????????
There's no way currently to set the default route in docker or to set the priority it uses. Rather the default route and priority is currently selected based on the alphabet of the network name.Real ????????????????
I'm not sure I understand what you're asking?
I read this post and it saved me a lot of time. I had spent several days trying to resolve issues with the default routing in Docker between two networks. The problem was that Docker uses routes based on the network name, rather than the order of the networks that I provided. This approach was not logical. I spent a few days investigating why the correct configuration didn't work. It was really surprising to see the approach chosen by the Docker developers.
From: Daniel @.> Sent: Sunday, May 12, 2024 12:15:55 AM To: docker/roadmap @.> Cc: YuriyTigiev @.>; Comment @.> Subject: Re: [docker/roadmap] The ability to select the default docker network route and configure network route priority (Issue #658)
There's no way currently to set the default route in docker or to set the priority it uses. Rather the default route and priority is currently selected based on the alphabet of the network name.
Real ????????????????
I'm not sure I understand what you're asking?
— Reply to this email directly, view it on GitHubhttps://github.com/docker/roadmap/issues/658#issuecomment-2106009407, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFNSYQSMFPM64CHHIK4CEM3ZBZ37PAVCNFSM6AAAAABG6RRHGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGAYDSNBQG4. You are receiving this because you commented.Message ID: @.***>
I read this post and it saved me a lot of time. I had spent several days trying to resolve issues with the default routing in Docker between two networks. The problem was that Docker uses routes based on the network name, rather than the order of the networks that I provided. This approach was not logical. I spent a few days investigating why the correct configuration didn't work. It was really surprising to see the approach chosen by the Docker developers.
From: Daniel @.> Sent: Sunday, May 12, 2024 12:15:55 AM To: docker/roadmap @.> Cc: YuriyTigiev @.>; Comment @.> Subject: Re: [docker/roadmap] The ability to select the default docker network route and configure network route priority (Issue #658)
There's no way currently to set the default route in docker or to set the priority it uses. Rather the default route and priority is currently selected based on the alphabet of the network name.
Real ????????????????
I'm not sure I understand what you're asking?
— Reply to this email directly, view it on GitHubhttps://github.com/docker/roadmap/issues/658#issuecomment-2106009407, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFNSYQSMFPM64CHHIK4CEM3ZBZ37PAVCNFSM6AAAAABG6RRHGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGAYDSNBQG4. You are receiving this because you commented.Message ID: @.***>
I too spent days troubleshooting an issue until I stumbled upon a really old docker forums post that explained this behavior.
What a bummer, just wasted a few hours...
Hope this will become configurable in the not so far future!
Even using the describer instead of the name would already be a huge progress, because that way I would not need to rename a centrally defined Network-Name but could just change it in a compose file. like so:
networks:
a_eth1.50:
ipv4_address: xx.xx.1y1.94
b_eth1.90:
ipv4_address: xx.xx.1zz1.94
networks:
a_eth1.50:
external: true
name: B-name
b_eth1.90:
external: true
name: A-Name
best case you'ld add a 'primary_route' parameter that could simply be added to one of the networks...
If after all this time the devs think we are not defining our container and their networking correctly to need this feature, then PLEASE point us to documentation of how it is supposed to be done.
Hey all, how hard is it to move over to kubernetes with multiple docker files and networks set up? I GUARANTEE that they have a feature like this.
Being able to set a default route is critical, and for both ipv4 and ipv6. Please implement this feature!