[MESOS-2674] Healthcheck command needs to be able to execute inside task container

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.22.0
• Component/s: docker
• Assignee: Unassigned
• Reporter: David McKinley
• Created: 29/Apr/15 14:16
• Updated: 05/Sep/15 14:00
• Resolved: 05/Sep/15 14:00

Description

When using the docker containerizer, executing a healthcheck command outside of the container running the task is not ideal. In some environments, such as CoreOS, the mesos-slave may be running in its own container, so then the healthcheck command runs in a separate container from the task.

There needs to be a way to run commands within the deployed task container, which can do the health assessment. If the container ID was available to the command (e.g., as an environment variable), this could potentially be accomplished by running a "docker exec" command for the Healthcheck. A cleaner solution, though, would cause the user-specified command to directly run within the appropriate container for the task.

Issue Links

• duplicates: MESOS-3136 COMMAND health checks with Marathon 0.10.0 are broken