[
https://issues.apache.org/jira/browse/YARN-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398121#comment-15398121
]
Shane Kumpf commented on YARN-5366:
-----------------------------------
After doing additional testing here, adding --rm to docker run will not work.
Detached mode combined with cleanup container on exit options are not supported
together. As a result, we'll need a bit more control over the lifecycle.
The high level lifecycle is:
received SIGKILL, SIGQUIT, SIGTERM?
does container exist?
is the container running?
docker stop
!keep exited container?
docker rm
To achieve this, we'll need to introduce docker rm and docker inspect. The
docker rm logic will also be removed from container executor and handled by
signalContainer.
I'll get a patch up soon that implements the above.
> Add support for toggling the removal of completed and failed docker containers
> ------------------------------------------------------------------------------
>
> Key: YARN-5366
> URL: https://issues.apache.org/jira/browse/YARN-5366
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Shane Kumpf
> Assignee: Shane Kumpf
>
> Currently, completed and failed docker containers are removed by
> container-executor. Add a job level environment variable to
> DockerLinuxContainerRuntime to allow the user to toggle whether they want the
> container deleted or not and remove the logic from container-executor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
