You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ podman-compose version
➤ podman compose version
>>>> Executing external compose provider "/usr/bin/podman-compose". Please see podman-compose(1) for how to disable this message. <<<<
podman-compose version: 1.0.6
['podman', '--version', '']
using podman version: 5.2.2
podman-compose version 1.0.6
podman --version
podman version 5.2.2
exit code: 0
$ podman-compose up
exit code: 0
podman start -a service1
[service1] | Hello from service1
exit code: 0
podman start -a service2
[service2] | Hello from service2
exit code: 0
Environment:
OS: Linux
podman version: 5.2.2
podman compose version: 1.0.6
The text was updated successfully, but these errors were encountered:
Describe the bug
A service that depends on the health of another service starts even though the service is not healthy.
To Reproduce
Steps to reproduce the behavior:
docker-compose.yml
,.env
,Dockerfile
, ...etc.)I typed this command:
Expected behavior
I would expect only service1 to start as the health check of service1 is
exit 1
(which refers to unhealthy - the container isn't working correctly: https://docs.docker.com/reference/dockerfile/#healthcheck)Actual behavior
Both service1 and service2 start.
Output
Environment:
The text was updated successfully, but these errors were encountered: