{"action":"created","issue":{"url":"https://api.github.com/repos/zalando-stups/taupage/issues/136","labels_url":"https://api.github.com/repos/zalando-stups/taupage/issues/136/labels{/name}","comments_url":"https://api.github.com/repos/zalando-stups/taupage/issues/136/comments","events_url":"https://api.github.com/repos/zalando-stups/taupage/issues/136/events","html_url":"https://github.com/zalando-stups/taupage/issues/136","id":110220087,"number":136,"title":"Rerunning a docker container inside Taupage","user":{"login":"dryewo","id":3134153,"avatar_url":"https://avatars.githubusercontent.com/u/3134153?v=3","gravatar_id":"","url":"https://api.github.com/users/dryewo","html_url":"https://github.com/dryewo","followers_url":"https://api.github.com/users/dryewo/followers","following_url":"https://api.github.com/users/dryewo/following{/other_user}","gists_url":"https://api.github.com/users/dryewo/gists{/gist_id}","starred_url":"https://api.github.com/users/dryewo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dryewo/subscriptions","organizations_url":"https://api.github.com/users/dryewo/orgs","repos_url":"https://api.github.com/users/dryewo/repos","events_url":"https://api.github.com/users/dryewo/events{/privacy}","received_events_url":"https://api.github.com/users/dryewo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-10-07T12:56:19Z","updated_at":"2015-10-09T08:55:56Z","closed_at":null,"body":"Please add some mechanism to rerun a docker container without restarting the machine itself.\r\nIt can be done manually by SSHing into the machine (using even and odd), then by grepping \"docker run\" from /var/log/syslog and then executing\r\n```\r\ndocker rm -fv $image && docker run ...\r\n```\r\nThat works perfectly, but it's not a reliable way to do programmatically, app-to-app.\r\nWe need this, for example, for cleaning up Jenkins slave after the job is built."},"comment":{"url":"https://api.github.com/repos/zalando-stups/taupage/issues/comments/146804814","html_url":"https://github.com/zalando-stups/taupage/issues/136#issuecomment-146804814","issue_url":"https://api.github.com/repos/zalando-stups/taupage/issues/136","id":146804814,"user":{"login":"dryewo","id":3134153,"avatar_url":"https://avatars.githubusercontent.com/u/3134153?v=3","gravatar_id":"","url":"https://api.github.com/users/dryewo","html_url":"https://github.com/dryewo","followers_url":"https://api.github.com/users/dryewo/followers","following_url":"https://api.github.com/users/dryewo/following{/other_user}","gists_url":"https://api.github.com/users/dryewo/gists{/gist_id}","starred_url":"https://api.github.com/users/dryewo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dryewo/subscriptions","organizations_url":"https://api.github.com/users/dryewo/orgs","repos_url":"https://api.github.com/users/dryewo/repos","events_url":"https://api.github.com/users/dryewo/events{/privacy}","received_events_url":"https://api.github.com/users/dryewo/received_events","type":"User","site_admin":false},"created_at":"2015-10-09T08:55:56Z","updated_at":"2015-10-09T08:55:56Z","body":"@hjacobs There is no underlying problem. Our use case is to let the Jenkins master (on one EC2 instance) connect to the slave container(on another EC2 instance), run an arbitrary job in it, take the result and disconnect.\r\nAfter that the container should be cleaned up of all intermediate build job results and side effects. This of course can be achieved by restarting the slave EC2 instance, but it takes much longer than just rerunning the container inside it.\r\nFor ideal reproduceability of build jobs we need it."}}