docker error : the input device is not a TTY. If you are using mintty, try prefixing the command with 'winpty'

After I run this
$ docker run --rm -v "/c/users/vipul rao/documents/github/wappalyzer:/opt/wappalyzer" -it wappalyzer/dev

I am getting the following error

> the input device is not a TTY. If you are using mintty, try prefixing the command with 'winpty'

What should I use here? I am running Docker on Windows 8 in MINGW64.

As suggested by the error message you obtain, you should try to use winpty (which is installed by default with Git-Bash) and thus run:

winpty docker run --rm -v "/c/users/vipul rao/documents/github/wappalyzer:/opt/wappalyzer" -it wappalyzer/dev

If this works, you may want to set a Bash alias to avoid manually prepending winpty all the time:

echo "alias docker='winpty docker'" >> ~/.bashrc

or

echo "alias docker='winpty docker'" >> ~/.bash_profile

If you are using Git Bash you can try like this

winpty docker run -it ubuntu

This problem occurs when running with -it option using bash terminal on windows. You can use Powershell to resolve this issue.

This works for me. I am using git bash on windows

winpty docker-compose exec app ls -l

Remove -it from the command. If you want to keep it interactive then keep -i

Don't use alias docker="winpty docker". It solves your problem but break pipes.

$ winpty docker run -ti ubuntu
root@e85cff7d1670:/# exit

$ wintpy docker run ubuntu bash HELLO 
HELLO

$ wintpy docker run ubuntu bash HELLO | cat
stdout is not a tty

Copy this to your .bashrc. This script uses winpty docker only if -ti is used.

function docker(){
  for param; do if [[ "$param" == "-ti" ]] || [[ "$param" == "-it" ]]; then 
    winpty docker "$@"; return
  fi; done; 
  command docker "$@"
}

docker run -ti ubuntu becomes winpty docker run -ti ubuntu avoids error: the input device is not a TTY. If you are using mintty, try prefixing the command with 'winpty'"

docker run ubuntu echo "what's up" | cat becomes command docker run echo "what'up" | cat avoids error: stdout is not a tty

The script only looks if there is a '-it' parameter without checking if it is inside a 'docker run' sentence... but it does the trick for my uses.

Did you start "Docker Quickstart Terminal"? I was trying to run

$ docker run -i -t redcricket/react-tutorial:latest /bin/bash

on windows from a Cygwin bash shell and got the same error:

the input device is not a TTY.  If you are using mintty, try prefixing the command with 'winpty'

Then I remembered that when I installed docker on my windows 10 system something called "Docker Quickstart Terminal" got installed. You need to start that first from that dumb windows 'Type here to search' thing on the task bar:

That launches this …

… you can run your docker commands there without getting that error or running winpty.

The problem is with gitbash however with the powershell it is working fine ..

Just add 'winpty' in start of your cmd ,Try below:

$ winpty docker.exe run --rm -v "/c/users/vipul rao/documents/github/wappalyzer:/opt/wappalyzer" -it wappalyzer/dev

Why this happens? More details here: http://willi.am/blog/2016/08/08/docker-for-windows-interactive-sessions-in-mintty-git-bash/

Got this error for running docker-compose exec workspace bash

So just prefix with winpty winpty docker-compose exec workspace bash

It may be that you're not running your commands within the Docker terminal. If you don't, you may not be properly connected to the Docker daemon and won't be able to interact correctly.

Make sure you're running commands in the actual Docker Terminal.

For those using WSL and running Docker for windows inside of cmder or conemu I would recommend to not to use Docker which is installed on windows in 'Program Files' but instead install Docker inside WSL on ubuntu/linux. Do remember though that you can't run Docker itself from within WSL, you must connect to Docker running on windows from the linux Docker client installed in WSL.

To install Docker on WSL

curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
sudo apt-get update
sudo apt-get install docker-ce

Your options for running actual Docker commands are to either: Connect to Docker using the switch -H

docker -H localhost:2375 run -it -v /mnt/c/code:/var/app -w "/var/app" centos:7

Or set the environment variable docker_host

export DOCKER_HOST=tcp://localhost:2375

Either way you are now be able to interactively connect to a running Docker container

Happened to me. From Git Bash, on Windows 8 running Docker Toolbox. There are two things happening. From git bash, we do not seem to have complete escalated privilege to the docker daemon (even though i'm running git bash with administrative privileges). Thus:

1. Try running the command from your docker terminal. (gives you privilege).

2. To compensate for errors from Window's folder naming formats, don't forget to quote the path.. (to escape spaces and/or capitalization errors) say

From:

docker run -v $(pwd):/data image_ref

To:

docker run -v "$(pwd):/data" image_ref

(notice the enclosing quotes in the latter around $(pwd):/data).

you can try with Cmder tool it will work. Its not working with Gitbash

In addition to above mentioned solutions. In case you are getting this error for docker attach

example: docker attach alpine1

error: the input device is not a TTY. If you are using mintty, try prefixing the command with 'winpty'

Solution: Adding winpty before docker command i.e. winpty docker attach should work.

example: winpty docker attach alpine1

Note: I was getting this error while using base on windows and this solution worked for me.

I had the same error when trying to run the docker-compose exec command. In the help documentation docker-compose exec --help it shows how you can disable the pseudo-tty allocation by adding -T to your command options in the following way:

docker-compose exec -T

From the help documentation:

-T Disable pseudo-tty allocation. By default docker-compose exec allocates a TTY.

If you are using gitbash the problem is when setting the terminal emulator for for using with Git bash.setting the emurator

Instead you can change the emulator to the first options or use the
winpty command before your docker run command