v2.20.1 Docker compose up often fails to join one random network

[BakasuraRCE]

Before you start please confirm the following.

• Yes, I've searched similar issues on GitHub.
• Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description

I run a stack and one or multiple containers in the compose has multiple networks, it often randomly fails to join exactly one network.

This is because portainer 2.20.1 use Docker compose 2.24.6 that have exactly this bug

docker/compose#11533
https://stackoverflow.com/questions/76719570/docker-compose-up-randomly-not-adding-containers-to-networks

I can confirm that the bug disappears in 2.20.2 that use docker compose v2.26.1

Expected Behavior

Join to all networks

Actual Behavior

Randomly fails to join exactly one network

Steps to Reproduce

1. Create a new stack with the file:

version: "3.8"
networks:
  test1:
  test2:
  test3:

services:
  whoami:
    image: traefik/whoami
    container_name: whoami
    networks:
      - test1
      - test2
      - test3

2. Check whoami networks(you will see one network missing in many cases)
3. stop and start again the stack
4. do steps 2 and 3 many times

Portainer logs or screenshots

No response

Portainer version

2.20.1

Portainer Edition

Business Edition (BE/EE) with 5NF / 3NF license

Platform and Version

Docker 26.1.1

OS and Architecture

Linux x64

Browser

No response

What command did you use to deploy Portainer?

No response

Additional Information

No response

[BakasuraRCE]

Maybe related with #11667

[jamescarppe]

So this bug occurs in 2.20.1 but is fixed in 2.20.2?

[BakasuraRCE]

yes

[jamescarppe]

As this is fixed in 2.20.2, this is a resolved issue and the fix is to update from 2.20.1 to 2.20.2.