{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/13742","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/13742/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/13742/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/13742/events","html_url":"https://github.com/kubernetes/kubernetes/issues/13742","id":105626146,"number":13742,"title":"Update to require Docker >= 1.7","user":{"login":"ncdc","id":354,"avatar_url":"https://avatars.githubusercontent.com/u/354?v=3","gravatar_id":"","url":"https://api.github.com/users/ncdc","html_url":"https://github.com/ncdc","followers_url":"https://api.github.com/users/ncdc/followers","following_url":"https://api.github.com/users/ncdc/following{/other_user}","gists_url":"https://api.github.com/users/ncdc/gists{/gist_id}","starred_url":"https://api.github.com/users/ncdc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ncdc/subscriptions","organizations_url":"https://api.github.com/users/ncdc/orgs","repos_url":"https://api.github.com/users/ncdc/repos","events_url":"https://api.github.com/users/ncdc/events{/privacy}","received_events_url":"https://api.github.com/users/ncdc/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/priority/P2","name":"priority/P2","color":"fbca04"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/node","name":"team/node","color":"d2b48c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2015-09-09T15:50:43Z","updated_at":"2015-09-10T04:32:56Z","closed_at":null,"body":"We should update the code base to require at least Docker 1.7. There are new features added to 1.7 that make CPU overcommit possible, and there is at least 1 bug with exec in 1.6.2 (kubectl exec -i <pod> bash, then type exit -> hangs) that is fixed in 1.7+.\r\n\r\n@smarterclayton @derekwaynecarr @dchen1107 @bgrant0607 @thockin @vishh @brendandburns @kubernetes/rh-cluster-infra @kubernetes/rh-platform-management "},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/139113481","html_url":"https://github.com/kubernetes/kubernetes/issues/13742#issuecomment-139113481","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/13742","id":139113481,"user":{"login":"thockin","id":5595220,"avatar_url":"https://avatars.githubusercontent.com/u/5595220?v=3","gravatar_id":"","url":"https://api.github.com/users/thockin","html_url":"https://github.com/thockin","followers_url":"https://api.github.com/users/thockin/followers","following_url":"https://api.github.com/users/thockin/following{/other_user}","gists_url":"https://api.github.com/users/thockin/gists{/gist_id}","starred_url":"https://api.github.com/users/thockin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thockin/subscriptions","organizations_url":"https://api.github.com/users/thockin/orgs","repos_url":"https://api.github.com/users/thockin/repos","events_url":"https://api.github.com/users/thockin/events{/privacy}","received_events_url":"https://api.github.com/users/thockin/received_events","type":"User","site_admin":false},"created_at":"2015-09-10T04:32:56Z","updated_at":"2015-09-10T04:32:56Z","body":"On Wed, Sep 9, 2015 at 4:11 PM, Dawn Chen <notifications@github.com> wrote:\n>\n\n> 3) Since it is open source, we cannot force all users to use qualified release(s). So the users running any docker releases other than 1.6.2 and with API above v1.15 are pretty on your own.\n\nSo we do not intend to qualify Docker 1.7 or 1.8 against kubernetes\nv1.0 - I appreciate that it is simple, I am worried that it will not\nbe good for real production users.\n\n> We are indeed committing to validating new docker releases. As a record, Kubernetes 1.1 release is having docker 1.7.1 by default at least. If we finish validation of docker 1.8, we are going to have docker 1.8.X by default.\n\nMy question was whether we qual new docker against older kube, and if\nso, how old?\n\n> I think a de facto \"three Kubelet\" is a right answer for our cluster-lifecycle story. But introducing \"tree docker\" is totally a different story:\n> 1) I didn't see any reason to run old docker version against the new kubernetes release (If docker new release has issues, we don't upgrade our default version and ask them to fix first) on our endorsed cloud providers.\n\nThe reason or SOME back-compat is that I don't buy that it's good for\nuser to demand they upgrade docker on our schedule.\n\n> Any objections? I am open to any suggestion here. cc/ @roberthbailey @zmerlynn\n\nI agree with the RedHat mode that 2 supported versions makes sense,\nwhat I don't have confidence in is the long-term support for old kube\nreleases.\n\nkubernetes v1.0.x will still be around and in use 12 months from now.\nDocker will be on 1.15 or something by then.  Are we telling users\nthat the only way to get a supported kubernetes version is to run a\nyear-old Docker?  Is that OK with users?\n\nThe alternative is that we qual each new docker against each\nkubernetes version - our qual tests are not that good yet.\n"}}