{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/12157","labels_url":"https://api.github.com/repos/docker/docker/issues/12157/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/12157/comments","events_url":"https://api.github.com/repos/docker/docker/issues/12157/events","html_url":"https://github.com/docker/docker/issues/12157","id":66984943,"number":12157,"title":"\"docker run --rm=true\" doesn't stop containers when ssh/net connection drops","user":{"login":"neurogenesis","id":613023,"avatar_url":"https://avatars.githubusercontent.com/u/613023?v=3","gravatar_id":"","url":"https://api.github.com/users/neurogenesis","html_url":"https://github.com/neurogenesis","followers_url":"https://api.github.com/users/neurogenesis/followers","following_url":"https://api.github.com/users/neurogenesis/following{/other_user}","gists_url":"https://api.github.com/users/neurogenesis/gists{/gist_id}","starred_url":"https://api.github.com/users/neurogenesis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/neurogenesis/subscriptions","organizations_url":"https://api.github.com/users/neurogenesis/orgs","repos_url":"https://api.github.com/users/neurogenesis/repos","events_url":"https://api.github.com/users/neurogenesis/events{/privacy}","received_events_url":"https://api.github.com/users/neurogenesis/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-04-07T20:38:55Z","updated_at":"2015-08-18T17:03:25Z","closed_at":"2015-04-07T20:44:30Z","body":"When launching an interactive container (like a gateway shell or rails console), the container is not stopped if the ssh/network connection is terminated.\r\n\r\nThere are probably cases both for and against leaving the container running, but if the user wants a persistent container they should use the -d option or launch \"docker run --rm\" from within screen/tmux.\r\n\r\nIf the containers aren't stopped & removed by default, this can cause a proliferation of running docker containers."},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/132280634","html_url":"https://github.com/docker/docker/issues/12157#issuecomment-132280634","issue_url":"https://api.github.com/repos/docker/docker/issues/12157","id":132280634,"user":{"login":"pwaller","id":438648,"avatar_url":"https://avatars.githubusercontent.com/u/438648?v=3","gravatar_id":"","url":"https://api.github.com/users/pwaller","html_url":"https://github.com/pwaller","followers_url":"https://api.github.com/users/pwaller/followers","following_url":"https://api.github.com/users/pwaller/following{/other_user}","gists_url":"https://api.github.com/users/pwaller/gists{/gist_id}","starred_url":"https://api.github.com/users/pwaller/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pwaller/subscriptions","organizations_url":"https://api.github.com/users/pwaller/orgs","repos_url":"https://api.github.com/users/pwaller/repos","events_url":"https://api.github.com/users/pwaller/events{/privacy}","received_events_url":"https://api.github.com/users/pwaller/received_events","type":"User","site_admin":false},"created_at":"2015-08-18T17:03:25Z","updated_at":"2015-08-18T17:03:25Z","body":"@jfrazelle I still think this issue is not covered by any open issue that I can find. Is there an issue which covers moving --rm to daemon side? #6757 was fixed by making it so that under the fail-to-create case the container is deleted server side, but as I understand it, does nothing for all of the other cases (such as the one originally stated in this issue).\r\n\r\nAlso, this is a real rats nest of long issues with lots of separate problems/solutions thrown in. I think docker could do with a clean proposal issue which outlines just moving the `docker run --rm` functionality server-side."}}