Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.0.0
-
None
-
Mesosphere Sprint 39
-
1
Description
When wrapping the health check command into docker exec, docker executor erroneously forms the health check command itself. Here is an excerpt from an executor log:
Launching health check process: docker exec mesos-2070f452-2120-45ad-a8d2-a339d234da41-S0.c27d1b78-d4aa-424b-91fa-1e91576db9b5 sh -c " true " /opt/mesosphere/packages/mesos--59d45b30116143cb8d9995ca26f9dec5e93dc710/libexec/mesos/mesos-health-check --executor=(1)@10.0.1.41:40651 --health_check_json={"command":{"shell":true,"value":"docker exec mesos-2070f452-2120-45ad-a8d2-a339d234da41-S0.c27d1b78-d4aa-424b-91fa-1e91576db9b5 sh -c \" true \""},"consecutive_failures":1,"delay_seconds":0.0,"grace_period_seconds":10.0,"interval_seconds":5.0,"timeout_seconds":10.0} --task_id=testhc.db69c60b-4a75-11e6-b9b0-c254ada9b06d