{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/BashOnWindows/issues/2379","repository_url":"https://api.github.com/repos/Microsoft/BashOnWindows","labels_url":"https://api.github.com/repos/Microsoft/BashOnWindows/issues/2379/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/BashOnWindows/issues/2379/comments","events_url":"https://api.github.com/repos/Microsoft/BashOnWindows/issues/2379/events","html_url":"https://github.com/Microsoft/BashOnWindows/issues/2379","id":246509813,"number":2379,"title":"Can not use docker.exe to run interactive docker containers from inside WSL, can not use arrow keys inside docker-compose.exe run containers","user":{"login":"veqryn","id":1897829,"avatar_url":"https://avatars0.githubusercontent.com/u/1897829?v=4","gravatar_id":"","url":"https://api.github.com/users/veqryn","html_url":"https://github.com/veqryn","followers_url":"https://api.github.com/users/veqryn/followers","following_url":"https://api.github.com/users/veqryn/following{/other_user}","gists_url":"https://api.github.com/users/veqryn/gists{/gist_id}","starred_url":"https://api.github.com/users/veqryn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/veqryn/subscriptions","organizations_url":"https://api.github.com/users/veqryn/orgs","repos_url":"https://api.github.com/users/veqryn/repos","events_url":"https://api.github.com/users/veqryn/events{/privacy}","received_events_url":"https://api.github.com/users/veqryn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-07-29T08:58:17Z","updated_at":"2017-07-29T15:13:54Z","closed_at":null,"body":"Can not use docker.exe to run interactive docker containers from inside WSL, can not use arrow keys inside docker-compose.exe run containers.\r\n\r\n* Your Windows build number:  Microsoft Windows [Version 10.0.15063]\r\n\r\n* What you're doing and what's happening:\r\nFrom inside WSL Bash:\r\n```bash\r\n02:42:50 ~$ which docker.exe\r\n/mnt/c/Program Files/Docker/Docker/resources/bin/docker.exe\r\n02:42:56 ~$ docker.exe --version\r\nDocker version 17.06.0-ce, build 02c1d87\r\n\r\n02:44:33 ~$ docker.exe run -it ubuntu:16.04 /bin/bash\r\nthe input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'\r\n02:45:16 ~$ winpty docker.exe run -it ubuntu:16.04 /bin/bash\r\nwinpty: command not found\r\n\r\n02:46:01 ~$ cmd.exe /c chcp 437\r\nActive code page: 437\r\n02:46:56 ~$ docker-compose.exe --version\r\ndocker-compose version 1.14.0, build c7bdf9e3\r\n02:47:14 ~$ docker-compose.exe run my-ubuntu /bin/bash\r\nStarting my-ubuntu ... done\r\nbash-4.2#\r\n\r\nbash-4.2#\r\n\r\nbash-4.2# pwd\r\npwd\r\n/\r\nbash-4.2# ^[[A^[[A^[[B^[[A\r\n```\r\n\r\nThat last line is me hitting the UP-Arrow key, expecting to see `pwd` fill my command prompt, but instead getting a bunch of `^[[A^[[A^[[B^[[A`\r\n\r\n* What's wrong / what should be happening instead:\r\n\r\nI would expect that I could use the native windows docker.exe to run interactive containers and also exec into containers.\r\nI'm not sure why docker.exe complains but docker-compose.exe does not complain.\r\n\r\nI would also expect that docker-compose run (interactively) would behavior normally, instead of printing out all my commands, extra line returns, and not letting me use the UP-Arrow to navigate previous commands.\r\n\r\nI had greatly hoped to be able to use the windows docker executables already installed on my system.\r\n\r\nInstead, in order to get my desired behavior, I had to install the linux docker executables into WSL, and then expose the Docker Daemon TCP Host on localhost (which is a security issue!), and then point the linux docker executables at it (ie: the way people did docker in wsl before the creator's update).\r\n"},"comment":{"url":"https://api.github.com/repos/Microsoft/BashOnWindows/issues/comments/318837468","html_url":"https://github.com/Microsoft/BashOnWindows/issues/2379#issuecomment-318837468","issue_url":"https://api.github.com/repos/Microsoft/BashOnWindows/issues/2379","id":318837468,"user":{"login":"fpqc","id":6083371,"avatar_url":"https://avatars2.githubusercontent.com/u/6083371?v=4","gravatar_id":"","url":"https://api.github.com/users/fpqc","html_url":"https://github.com/fpqc","followers_url":"https://api.github.com/users/fpqc/followers","following_url":"https://api.github.com/users/fpqc/following{/other_user}","gists_url":"https://api.github.com/users/fpqc/gists{/gist_id}","starred_url":"https://api.github.com/users/fpqc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fpqc/subscriptions","organizations_url":"https://api.github.com/users/fpqc/orgs","repos_url":"https://api.github.com/users/fpqc/repos","events_url":"https://api.github.com/users/fpqc/events{/privacy}","received_events_url":"https://api.github.com/users/fpqc/received_events","type":"User","site_admin":false},"created_at":"2017-07-29T15:13:54Z","updated_at":"2017-07-29T15:13:54Z","body":"@veqryn This is a docker.exe issue, I believe.  It is not aware of the new console functionality and probably duplicates it to some degree.  We saw similar problems on [Win32-OpenSSH](/PowerShell/Win32-OpenSSH).  Basically, when compiling docker.exe, they need to flip a few console flags up on the IO handles and disable their built-in terminal emulation code to allow the Windows console to take over processing."}}
{"actor":{"display_login":"fpqc"}}