Docker Community Forums

Share and learn in the Docker community.

How to check if the service is healthy

(Thschoen) #1


I created a service in my docker swarm (17.06.0-ce):

docker service create --mode=global --name=web nginx

When I check the service, i get this information:

docker service ls
ID              NAME   MODE      REPLICAS IMAGE       PORTS
6m8rro8rwtup    web    global    4/4      nginx:latest

How can I check if the service is completly healthy? I don’t want to check with docker ps the state on every node.
If I see preplicas 4/4, does it mean that all containers of my service on all nodes are healthy (also a defined healthcheck is checked)?
In that case I just can check the replicas?

if(replicas.equals("4/4")) {
   return "service is healthy;
} else {
   return "service is unhealthy";

(Werner Dijkerman) #2

Have you taken a look at “healthchecks” ? See and the options that starts with --health

(Thschoen) #3

I added a healthcheck to my dockerfile. I can check the status on every node with “docker ps my_application”, but I would like to check the status of the service, the command “docker service ps my_application” doesn’t tell me if my application is healty on every node.

(Mrhatken) #4

I am interested in this too. I think we need to define what a healthy service is in respect to the health of task (containers running) in that service.

With ps I can see that all services has the right number of tasks running but I cannot tell if those tasks are health without checking ps or logs.

It seems to me I have to find out the node for each task, then ssh there and inspect the docker container to check the health status of each task.

(Mrhatken) #5

Any solution to this? To check the health status of a service (not individually each running container in the service)…

(Mrhatken) #6

I wrote a script that determines the running containers for each service and which hosts they are on and then connects to that host with ssh and does a docker ps to get the status and health report.

It then reports back for each service (well if you use “apply dshc service1 service2 …”) the health of each running container for that service in a list. It’s slow but does give an overview of the health of each service.

It will be problematic, of course, if the container is not running successfully and jumping from host to host. It will show, however, the distinction between containers that are running and healthy or not.

Another reformulation of the question and clunky solution script here:

(Werner Dijkerman) #7

Isn’t is simpler to make use of Consul? (

(Archimedes Trajano) #8

I notice that if the service is not healthy according to the healthcheck the swarm will shut it down and restart it again. helps me visualize it.

As for healthchecks sometimes a simple nc localhost port < /dev/null is enough for what i need but I can also do a curl

And you do all this within the docker toolkit no additional tools except for that small monitoring image.

(Pablolibo) #9


When you create the service use the opt --detach=false


docker service create --mode=global --name=web --detach=false nginx


docker service update --detach=false name_service