Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
Mesosphere Sprint 76
-
2
Description
When deploying a marathon app with Docker Containerizer (need to check Mesos Containerizer) and the parameter name set, Mesos is not able to recognize/control/kill the started container.
Steps to reproduce
- Deploy the below marathon app definition
- Watch task being stuck in staging and mesos not being able to kill it/communicate with it
e.g., Agent Logs: W0126 18:38:50.000000 4988 slave.cpp:6750] Failed to get resource statistics for executor ‘instana-agent.1a1f8d22-02c8-11e8-b607-923c3c523109’ of framework 41f1b534-5f9d-4b5e-bb74-a0e387d5739f-0001: Failed to run ‘docker -H unix:///var/run/docker.sock inspect mesos-1c6f894d-9a3e-408c-8146-47ebab2f28be’: exited with status 1; stderr=’Error: No such image, container or task: mesos-1c6f894d-9a3e-408c-8146-47ebab2f28be
- Check on node and see container running, but not being recognized by mesos
{ "id": "/docker-test", "instances": 1, "portDefinitions": [], "container": { "type": "DOCKER", "volumes": [], "docker": { "image": "ubuntu:16.04", "parameters": [ { "key": "name", "value": "myname" } ] } }, "cpus": 0.1, "mem": 128, "requirePorts": false, "networks": [], "healthChecks": [], "fetch": [], "constraints": [], "cmd": "sleep 1000" }
Attachments
Attachments
Issue Links
- depends upon
-
MESOS-8640 Validate `DockerInfo` exists when container's type is `DOCKER`
- Resolved