compose
compose copied to clipboard
Waiting for healthy container not showing in the terminal
Description
I have a docker-compose.yml where I have healthchecks for redis and other containers have to wait till redis is healthy.
This seems to work, but in the past the terminal would show how many time has passed till the container is healthy.
This seems to be gone and the terminal doesnt show the time passed.
It stays showing this view without the seconds on the right moving / counting.
Steps To Reproduce
No response
Compose Version
Docker Compose version v2.21.0-desktop.1
Docker Environment
Client: Docker Engine - Community
Version: 24.0.6
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.2-desktop.4
Path: /usr/local/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.21.0-desktop.1
Path: /usr/local/lib/docker/cli-plugins/docker-compose
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /usr/local/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: /usr/local/lib/docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.7
Path: /usr/local/lib/docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /usr/local/lib/docker/cli-plugins/docker-sbom
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: /usr/local/lib/docker/cli-plugins/docker-scan
scout: Docker Scout (Docker Inc.)
Version: v1.0.8
Path: /home/alves/.docker/cli-plugins/docker-scout
Server:
Containers: 6
Running: 6
Paused: 0
Stopped: 0
Images: 3
Server Version: 24.0.6
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
runc version: v1.1.8-0-g82f18fe
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.90.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.42GiB
Name: docker-desktop
ID: 926200dc-d496-4c01-bbe3-866b25281c7f
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile
Anything else?
No response
Hello, @K2ouMais, I was investigating this issue and I ran:
docker compose up -d
and then check the current status of the containers with
docker ps
and I can see with both versions the (heath: starting...)
and so on under status. So I am not entirely sure how to reproduce your issue. Could you be more specific with the commands you are running and some screenshots of what you are experiencing?
Hello @jhrotko,
what I meant is, in the past when using the command docker compose up -d
you could see the timer (seconds) (see right side) like in my screenshot running when it was waiting for a containers health-check to pass.
The time would still run the seconds, till the container was "healthy".
With the newer updates, you can see that the containers are starting, but the seconds on the right side are stopped, so that you dont know if it is still waiting for a healthy container (redis / mysql and so on) or not.
Fixed in https://github.com/docker/compose/pull/11357
@jhrotko
After updating to Docker Desktop 4.29.0 this is broken again