Docker - the input device is not a TTY
See original GitHub issueI’m trying to run my tests on a TFS build. However, I got the following error:
the input device is not a TTY
I know that this is related to -it
flag on docker run
command, but I’m afraid that i cannot remove this flag without submitting a PR (I dont know why backstop uses -it
also) and I cannot activate tty on the server in which TFS is running.
Any ideas about that?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Error "The input device is not a TTY" - Stack Overflow
However, I get the error "The input device is not a TTY". docker run -v $PWD:/foobar -it cloudfoundry/cflinuxfs2 /foobar/script.sh. Is there a ...
Read more >docker error in crontab: the input device is not a TTY
when you run a docker command via crontab like below # /usr/bin/docker exec -it containername /path/to/command. you will get “the input device is...
Read more >What does "the input device is not a TTY" exactly mean in ...
Late answer, but might help someone. docker run/exec -i will connect the STDIN of the command inside the container to the STDIN of...
Read more >docker-compose exec: the input device is not a TTY #7306
Description of the issue Cannot start interactive shell (e.g. /bin/bash) using docker-compose -f - exec Context information (for bug ...
Read more >[SOLVED] Docker The Input Device Is Not A TTY Error
In this post I will show you the super easy solution for error: Docker The input device is not a TTY! This error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, definitely.
I actually was thinking in trying something like this:
"dockerOptions": { "args": ["-it"] }
I agree @garris, this is the right way to do it, I’d prefer this over my PR.