{"action":"created","issue":{"url":"https://api.github.com/repos/gliderlabs/logspout/issues/106","labels_url":"https://api.github.com/repos/gliderlabs/logspout/issues/106/labels{/name}","comments_url":"https://api.github.com/repos/gliderlabs/logspout/issues/106/comments","events_url":"https://api.github.com/repos/gliderlabs/logspout/issues/106/events","html_url":"https://github.com/gliderlabs/logspout/issues/106","id":83814895,"number":106,"title":"Change to docker 1.7 events breaks logspout","user":{"login":"phobologic","id":517334,"avatar_url":"https://avatars.githubusercontent.com/u/517334?v=3","gravatar_id":"","url":"https://api.github.com/users/phobologic","html_url":"https://github.com/phobologic","followers_url":"https://api.github.com/users/phobologic/followers","following_url":"https://api.github.com/users/phobologic/following{/other_user}","gists_url":"https://api.github.com/users/phobologic/gists{/gist_id}","starred_url":"https://api.github.com/users/phobologic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/phobologic/subscriptions","organizations_url":"https://api.github.com/users/phobologic/orgs","repos_url":"https://api.github.com/users/phobologic/repos","events_url":"https://api.github.com/users/phobologic/events{/privacy}","received_events_url":"https://api.github.com/users/phobologic/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-06-02T03:31:23Z","updated_at":"2015-06-05T17:44:10Z","closed_at":null,"body":"Due to this bug:\r\n\r\nhttps://github.com/docker/docker/issues/12848#issuecomment-99530374\r\n\r\nI have had to use docker 1.7 in my project, or else face running out of memory rapidly.\r\n\r\nWhile implementing logspout (via the docker container, gliderlabs/logspout:master) with docker 1.7, I noticed that a restart of logspout would cause it to crash repeatedly at this line with containers that weren't listed in `docker ps`:\r\n\r\nhttps://github.com/gliderlabs/logspout/blob/master/router/pump.go#L124\r\n\r\nIt took a bit, but finally I tracked it down to this change to the events code in docker 1.7:\r\n\r\nhttps://github.com/docker/docker/blob/master/daemon/events/events.go#L28\r\n\r\nBasically it looks like the events endpoint now returns the last 64 events and then starts tailing the events.  The logspout daemon was crashing because it was working through the past 64 events, and it hit the event that said that the old logspout daemon had just come up.\r\n\r\nI want to go ahead and make an attempt at fixing this issue, but first I figured I'd get some people's take on what the behavior should be."},"comment":{"url":"https://api.github.com/repos/gliderlabs/logspout/issues/comments/109376060","html_url":"https://github.com/gliderlabs/logspout/issues/106#issuecomment-109376060","issue_url":"https://api.github.com/repos/gliderlabs/logspout/issues/106","id":109376060,"user":{"login":"phobologic","id":517334,"avatar_url":"https://avatars.githubusercontent.com/u/517334?v=3","gravatar_id":"","url":"https://api.github.com/users/phobologic","html_url":"https://github.com/phobologic","followers_url":"https://api.github.com/users/phobologic/followers","following_url":"https://api.github.com/users/phobologic/following{/other_user}","gists_url":"https://api.github.com/users/phobologic/gists{/gist_id}","starred_url":"https://api.github.com/users/phobologic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/phobologic/subscriptions","organizations_url":"https://api.github.com/users/phobologic/orgs","repos_url":"https://api.github.com/users/phobologic/repos","events_url":"https://api.github.com/users/phobologic/events{/privacy}","received_events_url":"https://api.github.com/users/phobologic/received_events","type":"User","site_admin":false},"created_at":"2015-06-05T17:44:10Z","updated_at":"2015-06-05T17:44:10Z","body":"Oh, sorry, I think I'm getting the comment stream mixed up :)"}}