[BUG] Inconsistent output in docker compose up -d after v5.0.0 upgrade

[mkhalil-twipi]

Description

After upgrading to Docker Compose v5.0.0, docker compose up -d shows
inconsistent output. Running the command multiple times shows different
containers each time, or no output at all, even though all containers
are running.

Related PR: #13357

Steps To Reproduce

1. Run docker compose up -d → Shows some containers
2. Run docker compose up -d immediately after → Shows nothing
3. Run again → Shows different containers

Compose Version

Docker Compose version v5.0.0

Docker Environment

Client: Docker Engine - Community
 Version:    29.1.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.30.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.0.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Anything else?

No response

[ndeloof]

I can't reproduce. Can you share your compose file?

[onvik]

I have the same issue.

% docker info  
Client: Docker Engine - Community
 Version:    29.1.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.30.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.0.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Sometimes it outputs nothing, or only some of the containers.

% docker compose up -d     
[+] up 3/3
 ✔ Container prometheus Running                                                                                                       0.0s 
 ✔ Container grafana    Running                                                                                                       0.0s 
 ✔ Container netdata    Running

%  docker compose up -d
[+] up 3/3

% docker compose up -d
[+] up 3/3
 ✔ Container prometheus Running

There is another issue which might be related to this.

[Pallandos]

Same here on this version :

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04.3 LTS
Release:	24.04
Codename:	noble

$ docker compose version
Docker Compose version v5.0.0

$ docker info
Client: Docker Engine - Community
 Version:    29.1.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.30.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.0.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

On my side, i am also affected when running docker compose down. Sometimes the spinner freezes,
sometimes a container is not listed, sometimes it even disappears when the command ends.

[ndeloof]

One possible reason is that some container are being started during the up sequence. To avoid conflict between container initial logs and progress UI, Start events are ignored so the progress UI won't display any detail

[onvik]

#13439 fixes this issue

[virtualstaticvoid]

I'm seeing a similar issue where the terminal is left in an semi-unusable state after running docker compose.

The command appears to still be running, but it has actually completed.

After pressing Enter a few times, the shell prompt ($) becomes visible again, confirming the command
has exited. However, the terminal remains broken:

• The cursor is no longer blinking
• Input is not echoed correctly
• Pressing ENTER several times reveals the prompt

Expected behavior

After the command completes, the terminal should return to a normal interactive state with a visible
cursor and functional input.

Actual behavior

The shell prompt eventually returns, but the terminal remains in a corrupted state, requiring a new
terminal window to continue working.

$ docker version
Client: Docker Engine - Community
 Version:           29.1.3
 API version:       1.52
 Go version:        go1.25.5
 Git commit:        f52814d
 Built:             Fri Dec 12 14:49:32 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          29.1.3
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.5
  Git commit:       fbf3ed2
  Built:            Fri Dec 12 14:49:32 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.2.0
  GitCommit:        1c4457e00facac03ce1d75f7b6777a7a851e5c41
 runc:
  Version:          1.3.4
  GitCommit:        v1.3.4-0-gd6d73eb8
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ docker compose version
Docker Compose version v5.0.0

[ndeloof]

@virtualstaticvoid unrelated, see #13420

[ndeloof]

Closing as "fixed by #13439"
Maybe there's multiple UI issues here, so feel free to comment if you get some weird behavior which latest codebase (make install to test) doesn't already fixed

[GISVEN]

One possible reason is that some container are being started during the up sequence. To avoid conflict between container initial logs and progress UI, Start events are ignored so the progress UI won't display any detail

Is there a way to get this behavior back? Especially this part "Start events are ignored so the progress UI won't display any detail" It was very usefull to see which containers affected and started. Maybe there are some workarounds?