{"action":"opened","issue":{"url":"https://api.github.com/repos/docker/docker/issues/15274","labels_url":"https://api.github.com/repos/docker/docker/issues/15274/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/15274/comments","events_url":"https://api.github.com/repos/docker/docker/issues/15274/events","html_url":"https://github.com/docker/docker/issues/15274","id":98852219,"number":15274,"title":"'exec -i containerid sh -c read a' is flaky on Windows under docker test","user":{"login":"jhowardmsft","id":10522484,"avatar_url":"https://avatars.githubusercontent.com/u/10522484?v=3","gravatar_id":"","url":"https://api.github.com/users/jhowardmsft","html_url":"https://github.com/jhowardmsft","followers_url":"https://api.github.com/users/jhowardmsft/followers","following_url":"https://api.github.com/users/jhowardmsft/following{/other_user}","gists_url":"https://api.github.com/users/jhowardmsft/gists{/gist_id}","starred_url":"https://api.github.com/users/jhowardmsft/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhowardmsft/subscriptions","organizations_url":"https://api.github.com/users/jhowardmsft/orgs","repos_url":"https://api.github.com/users/jhowardmsft/repos","events_url":"https://api.github.com/users/jhowardmsft/events{/privacy}","received_events_url":"https://api.github.com/users/jhowardmsft/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-03T22:44:14Z","updated_at":"2015-08-03T22:44:14Z","closed_at":null,"body":"See PR https://github.com/docker/docker/pull/14697. One of the reasons this test was failing so many times was that when running under docker test, the exec'd process exits almost immediately. My best guess at this time is that the daemon sees something on stdin, so it exits normally (debug spew on the daemon seems to indicate this is the case). \r\n\r\nWhile TestInspectExecID has been modified to workaround this issue, there probably should still be some investigation into why the specific command above fails when under docker test, and only from Windows. And probably a new explicit test written. "}}