[BUG] Per-layer pull progress restored by PR #13445 regressed

[Hujgo]

Description

The PR fix #13445 was merged to the v5.0.1 release.

Version 5.0.1

docker compose pull
[+] pull 3/15
 ⠙ Image itzg/minecraft-bedrock-server [⣤⣿⣀⣿⣿⣷⠀⠀⠀⠀⠀⠀⠀⠀] Pulling                                                    4.1s
   ⠹ 6e7932d5cb55                      Downloading [=========================>                         ]  25.33... 2.1s
   ✔ 916272152479                      Download complete                                                           0.8s
   ⠹ 7c0172621a99                      Downloading [================>                                  ]  18.34... 2.1s
   ✔ acc23003db80                      Download complete                                                           1.1s
   ✔ 45b75c2afcc1                      Download complete                                                           1.6s
   ⠹ 1969920581cf                      Downloading [=============================================>     ]  2.815... 2.1s
   ⠹ ec8f1a011f7f                      Waiting                                                                     2.1s
   ⠹ 6f749e3faf3e                      Waiting                                                                     2.1s
   ⠹ 112ca79ae9b2                      Waiting                                                                     2.1s
   ⠹ d8e3e91103e4                      Waiting                                                                     2.1s
   ⠹ 0b6fea94e715                      Waiting                                                                     2.1s
   ⠹ 963d2ab257ac                      Waiting                                                                     2.1s
   ⠹ 130ff748cd89                      Waiting                                                                     2.1s
   ⠹ a8c4e6c14a62                      Waiting                                                                     2.1s
^C
docker compose version
Docker Compose version v5.0.1

Version 5.1.3

docker compose pull
[+] pull 2/15
 ⠋ Image itzg/minecraft-bedrock-server [⣤⣿⣄⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling

Backtracking the releases, the issue appeared in Version 5.0.2 again
Version 5.0.2

docker compose pull
[+] pull 2/15
 ⠸ Image itzg/minecraft-bedrock-server [⡀⣿⡀⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀] Pulling   
^C
docker compose version
Docker Compose version v5.0.2

Steps To Reproduce

1. run docker compose pull

Compose Version

Docker Compose version v5.1.3

Docker Environment

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

Server:
 Containers: 29
  Running: 29
  Paused: 0
  Stopped: 0
 Images: 78
 Server Version: 29.4.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: journald
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 77c84241c7cbdd9b4eca2591793e3d4f4317c590
 runc version: v1.3.5-0-g488fc13e
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.12.75+rpt-rpi-2712
 Operating System: Debian GNU/Linux 13 (trixie)
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 15.84GiB
 Name: damos
 ID: a8515a4c-5289-49fa-b754-4d5569df0978
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false
 Firewall Backend: iptables

Anything else?

Same issue after the v5 update #13443

[KALI-THE-HACKER]

@Hujgo I was able to reproduce this regression in docker compose pull on versions ≥ v5.0.2, while v5.0.1 shows correct per-layer progress.

Since #13445 restored nested pull progress handling, this appears to be a regression introduced after that change.

I plan to investigate the progress event/state management around pull to identify what broke. Please let me know if there’s already work in progress, otherwise I can work on a fix and follow up with a PR.

[KALI-THE-HACKER]

@Hujgo Based on discussion with @ndeloof on Slack, the removal of per-layer progress output was an intentional change to simplify the UI, with the single-line output now reflecting progress via compact animation.

Given that, this may not be a regression but expected behavior since v5.0.2.