{"action":"created","issue":{"url":"https://api.github.com/repos/mauricioklein/docker-compose-api/issues/14","labels_url":"https://api.github.com/repos/mauricioklein/docker-compose-api/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/mauricioklein/docker-compose-api/issues/14/comments","events_url":"https://api.github.com/repos/mauricioklein/docker-compose-api/issues/14/events","html_url":"https://github.com/mauricioklein/docker-compose-api/issues/14","id":127650049,"number":14,"title":"docker-compose-api forgets which containers it has created between restarts","user":{"login":"jeroenj","id":76424,"avatar_url":"https://avatars.githubusercontent.com/u/76424?v=3","gravatar_id":"","url":"https://api.github.com/users/jeroenj","html_url":"https://github.com/jeroenj","followers_url":"https://api.github.com/users/jeroenj/followers","following_url":"https://api.github.com/users/jeroenj/following{/other_user}","gists_url":"https://api.github.com/users/jeroenj/gists{/gist_id}","starred_url":"https://api.github.com/users/jeroenj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeroenj/subscriptions","organizations_url":"https://api.github.com/users/jeroenj/orgs","repos_url":"https://api.github.com/users/jeroenj/repos","events_url":"https://api.github.com/users/jeroenj/events{/privacy}","received_events_url":"https://api.github.com/users/jeroenj/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mauricioklein/docker-compose-api/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":10,"created_at":"2016-01-20T10:19:17Z","updated_at":"2016-01-25T09:59:40Z","closed_at":null,"body":"When starting a container from a ruby process a container with a random name gets created. It keeps track of the container by using it's id in-memory.\r\nWhen exiting the ruby-process and starting a new process docker-compose-api obviously doesn't know which containers it started before. This causes it to create/start a new container when requested.\r\n\r\nI think that using named containers (https://github.com/mauricioklein/docker-compose-api/issues/13) might solve this problem. However if incremental names are used it might be a bit harder to tackle...\r\n\r\nI'd be happy to help you out with this as I'm building a ruby app which needs to manage a bunch of containers."},"comment":{"url":"https://api.github.com/repos/mauricioklein/docker-compose-api/issues/comments/174456499","html_url":"https://github.com/mauricioklein/docker-compose-api/issues/14#issuecomment-174456499","issue_url":"https://api.github.com/repos/mauricioklein/docker-compose-api/issues/14","id":174456499,"user":{"login":"jeroenj","id":76424,"avatar_url":"https://avatars.githubusercontent.com/u/76424?v=3","gravatar_id":"","url":"https://api.github.com/users/jeroenj","html_url":"https://github.com/jeroenj","followers_url":"https://api.github.com/users/jeroenj/followers","following_url":"https://api.github.com/users/jeroenj/following{/other_user}","gists_url":"https://api.github.com/users/jeroenj/gists{/gist_id}","starred_url":"https://api.github.com/users/jeroenj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeroenj/subscriptions","organizations_url":"https://api.github.com/users/jeroenj/orgs","repos_url":"https://api.github.com/users/jeroenj/repos","events_url":"https://api.github.com/users/jeroenj/events{/privacy}","received_events_url":"https://api.github.com/users/jeroenj/received_events","type":"User","site_admin":false},"created_at":"2016-01-25T09:59:40Z","updated_at":"2016-01-25T09:59:40Z","body":"Thanks a lot! If I find something missing for my current setup I'll be happy to contribute. :)"}}