Closed theoneandonly-vector closed 4 years ago
Hi @theoneandonly-vector,
thanks for your report. Just for the record you can see the output of a health check when running for example docker inspect --format "{{json .State.Health }}" $(docker-compose ps -q kopano_kustomer) | jq
. The command that is run as the health check is also part of the Dockerfile (at least for the images built by this project), you can see it for example at https://github.com/zokradonh/kopano-docker/blob/6521970f23ab6f2db8527abc53acd5ed59535514/webapp/Dockerfile#L85. These can then just be run in any running container to verify the output.
The kustomer container has a health check prepared, but not implemented. I have removed it in the upstream Dockerfile and pushed a new image with the latest tag. For webapp seems there is some breakage caused by the upgrade to buster in https://github.com/zokradonh/kopano-docker/pull/253.
I have created https://github.com/zokradonh/kopano-docker/pull/344 to fix this.
thank you so much :)
Describe the bug Two Containers shows as unhealthy when I check with "docker ps" kustomerd & kopano_webapp
Output of docker-compose logs $kustomerd:
Output of docker-compose logs $kopano_webapp::
To Reproduce Docker version 19.03.5, build 633a0ea838 docker-compose version 1.25.4, build 8d51620a
my docker-compose config:
Expected behavior docker ps should show all containers as "healthy"