Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-8488

Docker bug can cause unkillable tasks.

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Due to an issue on the Moby project, it's possible for Docker versions 1.13 and later to fail to catch a container exit, so that the docker run command which was used to launch the container will never return. This can lead to the Docker executor becoming stuck in a state where it believes the container is still running and cannot be killed.

      We should update the Docker executor to ensure that containers stuck in such a state cannot cause unkillable Docker executors/tasks.

      One way to do this would be a timeout, after which the Docker executor will commit suicide if a kill task attempt has not succeeded. However, if we do this we should also ensure that in the case that the container was actually still running, either the Docker daemon or the DockerContainerizer would clean up the container when it does exit.

      Another option might be for the Docker executor to directly wait() on the container's Linux PID, in order to notice when the container exits.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            qianzhang Qian Zhang
            greggomann Greg Mann
            Greg Mann Greg Mann
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Agile

                Completed Sprint:
                Mesosphere Sprint 74 ended 15/Feb/18
                View on Board

                Slack

                  Issue deployment