241a2913ec
containerd has two objects with regard to containers. There is a "container" object which is metadata and a "task" which is manging the actual runtime state. When docker starts a container, it creartes both the container metadata and the task at the same time. So when a container exits, docker deletes both of these objects as well. This ensures that if, on start, when we go to create the container metadata object in containerd, if there is an error due to a name conflict that we go ahead and clean that up and try again. Signed-off-by: Brian Goff <cpuguy83@gmail.com> (cherry picked from commit 5ba30cd1dc6000ee53b34f628cbff91d7f6d7231) Signed-off-by: Sebastiaan van Stijn <github@gone.nl> Upstream-commit: 1d0353548a21b0b60595ad44859a7072f90ea6c6 Component: engine