Update Docker and Docker Compose Dependencies

[Ian-Costa18]

Is your feature request related to a problem? Please describe

With the current STS release of Portainer, it is not possible to set the gateway priority for containers defined in templates. In my setup, I have a network where only one container (a reverse proxy) can access the others on the network, while all other connections are blocked. Some containers attempt to use that network and container's host names map to their IP address on that network.

Describe the solution you'd like

Docker Compose release 2.33.1 implements gw_priority which allows setting the default gateway a container uses to reach the internet and other containers. Portainer STS appears to use Docker v27.5.1 and Docker Compose v2.31.0. Updating Docker to at least v28 and Docker Compose to at least v2.33.1 would solve this issue for me.

Describe alternatives you've considered

I have attempted to change the order of the networks in the compose that creates the stack, but the behavior is not consistent. For now, I have updated the Docker and Docker Compose packages on my system and use Docker Compose with the gw_priority setting for the containers that need to be able to access other containers.

Additional context

No response

[MeCJay12]

I have the same issue

[tziuhtli]

I have a non-solution, rename your networks in the lexicographical order you want them to appear within a container.

I was chasing this problem down a couple months ago. Found the following [now deleted] quote here:

When a container is connected to multiple networks, its external connectivity is provided via the first non-internal network, in lexical order.

This post was what led me to it, a bit old but renaming solved it for me.

[InternetWorkAcct]

I hate it but it works

[nioc]

This is still very annoying...
I have a set of internal networks that do not access the internet (with --internal) and one network public-net that does.
I don't want all services on the public-net network to communicate directly with each other, so I added the -o "com.docker.network.bridge.enable_icc"=false.

As the rule is:

You can connect and disconnect running containers from networks without restarting the container. When a container is connected to multiple networks, its external connectivity is provided via the first non-internal network, in lexical order.

without gw_priority my HAProxy uses the only non-internal network (public-net) to access apps on the internal network... and fails (because of enable_icc=false by design).
It would be easier to be able to indicate which network to prioritize, but wait... this feature has been available in Docker for 5 months 😠

When will the update include the necessary version?