Lenfree Yeung created MESOS-8981:
------------------------------------
Summary: When Docker daemon restarts, Mesos slave does not know
about this container
Key: MESOS-8981
URL: https://issues.apache.org/jira/browse/MESOS-8981
Project: Mesos
Issue Type: Bug
Reporter: Lenfree Yeung
Mesos version: 1.0.0
Containerizer: Docker
Docker version: 17.09
OS: Ubuntu 16.04
Framework: Singularity
Recently I had to roll out a change on Docker daemon config which involves
restarting of Docker daemon.
Logs:
```bash
Executor for container '6d747a2c-3a52-4af6-b472-45e7603c0978' has exited
Destroying container '6d747a2c-3a52-4af6-b472-45e7603c0978'
Running docker stop on container '6d747a2c-3a52-4af6-b472-45e7603c0978'
To reproduce:
# Run an existing job
# Restart Docker daemon on this host where job is assigned to
# Mesos would picked this up and assign this job to another slave which is
expected behaviour.
# Run docker ps will show container running on host from step 1 but
Mesos/Scheduler only knows about the new job that was moved to new host.
Am I missing some configuration that address this? Mesos slave is running with
`--containerizers=docker,mesos`
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
