blocks|key|800968|text|正如您获得的错误消息所建议的那样，您应该尝试使用温蒂+(默认情况下安装在Git-Bash中)，然后运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|800969|winpty+docker+run+--rm+-v+"/c/users/vipul+rao/documents/github/wappalyzer:/opt/wappalyzer"+-it+wappalyzer/dev|code-block|syntax|javascript|800970|如果这样做有效，您可能希望设置一个Bash别名，以避免一直手动地在winpty前面加上以下内容：|style|CODE|800971|echo+"alias+docker='winpty+docker'"+>>+~/.bashrc|800972|或|800973|echo+"alias+docker='winpty+docker'"+>>+~/.bash_profile|800974|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/rprichard/winpty^0|O|2|0|0|0|X|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|15|8|@$A|16|B|17|K|L]]|9|@]|C|$]]|$1|M|3|N|5|F|7|18|8|@]|9|@]|C|$G|H]]|$1|O|3|P|5|6|7|19|8|@]|9|@]|C|$]]|$1|Q|3|R|5|F|7|1A|8|@]|9|@]|C|$G|H]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]]]

As suggested by the error message you obtain, you should try to use <a href="https://github.com/rprichard/winpty" rel="noreferrer">winpty</a> (which is installed by default with Git-Bash) and thus run:

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

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

<pre><code>echo "alias docker='winpty docker'" &gt;&gt; ~/.bashrc
</code></pre>

or

<pre><code>echo "alias docker='winpty docker'" &gt;&gt; ~/.bash_profile
</code></pre>

blocks|key|328488|text|如果您正在使用Git+Bash，您可以这样做|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328489|winpty+docker+run+-it+ubuntu|code-block|syntax|javascript|328490|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you are using Git Bash you can try like this

<pre><code>winpty docker run -it ubuntu
</code></pre>

blocks|key|328184|text|在windows上使用bash终端使用-it选项运行时会出现此问题。您可以使用Powershell解决此问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|328185|entityMap^0|J|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

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

blocks|key|328598|text|这对我有用。我在窗户上用git+bash|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328599|winpty+docker-compose+exec+app+ls+-l|code-block|syntax|javascript|328600|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This works for me.
I am using git bash on windows
<pre><code>winpty docker-compose exec app ls -l
</code></pre>

blocks|key|1599329|text|从命令中删除-it。如果您想保持它的交互性，那么保持-i|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1599330|entityMap^0|6|3|Q|2|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Remove <code>-it</code> from the command. If you want to keep it interactive then keep <code>-i</code>

blocks|key|1599662|text|不要使用alias+docker="winpty+docker"。它解决了你的问题，但打破了管道。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1599663|$+winpty+docker+run+-ti+ubuntu
root@e85cff7d1670:/#+exit

$+wintpy+docker+run+ubuntu+bash+HELLO+
HELLO

$+wintpy+docker+run+ubuntu+bash+HELLO+%7C+cat
stdout+is+not+a+tty|code-block|syntax|javascript|1599664|把这个拷贝到你的.bashrc。只有在使用winpty+docker时，此脚本才使用-ti。|1599665|function+docker(){
++for+param;+do+if+[[+"$param"+==+"-ti"+]]+%7C%7C+[[+"$param"+==+"-it"+]];+then+
++++winpty+docker+"$@";+return
++fi;+done;+
++command+docker+"$@"
}|1599666|docker+run+-ti+ubuntu变成winpty+docker+run+-ti+ubuntu避免了error:+the+input+device+is+not+a+TTY.++If+you+are+using+mintty,+try+prefixing+the+command+with+'winpty'"|1599667|docker+run+ubuntu+echo+"what's+up"+%7C+cat变成command+docker+run+echo+"what'up"+%7C+cat避免了error:+stdout+is+not+a+tty|1599668|脚本只在有'-+it‘参数时才会查看，而不检查它是否在'docker+run’语句中.但这对我的用途很有帮助。|1599669|entityMap^0|4|S|0|0|L|D|16|3|0|0|0|L|N|S|1I|2W|0|0|14|16|13|2C|Q|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1K|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|V|$]]

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

<pre><code>$ 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
</code></pre>

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

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

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

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

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.

blocks|key|801060|text|你启动“码头快速启动终端”了吗？我试着跑|type|unstyled|depth|inlineStyleRanges|entityRanges|data|801061|$+docker+run+-i+-t+redcricket/react-tutorial:latest+/bin/bash|code-block|syntax|javascript|801062|在来自Cygwin+bash+shell的窗口中，得到了相同的错误：|801063|the+input+device+is+not+a+TTY.++If+you+are+using+mintty,+try+prefixing+the+command+with+'winpty'|801064|然后我记得当我在我的windows+10系统上安装码头时，安装了一个叫做“码头快速启动终端”的系统。首先，您需要从任务栏上的哑窗口“输入此处搜索”开始：|801065|​|801066|📷|atomic|offset|length|801067|801068|启动这个…|801069|801070|801071|801072|…您可以在那里运行您的docker命令，而无需获得该错误或运行winpty。|801073|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/720a6afdc9d34c2cd1f24432f84fb829.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/daf77152963387d43e1b54bc6c1dae22.png^0|0|0|0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1E|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1F|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1G|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1I|8|@]|9|@$R|1J|S|1K|1|1L]]|A|$]]|$1|T|3|N|5|6|7|1M|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1N|8|@]|9|@]|A|$]]|$1|W|3|N|5|6|7|1O|8|@]|9|@]|A|$]]|$1|X|3|P|5|Q|7|1P|8|@]|9|@$R|1Q|S|1R|1|1S]]|A|$]]|$1|Y|3|N|5|6|7|1T|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1U|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18|19|-4]]|1A|$5|14|15|16|A|$17|1B|19|-4]]]]

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

<pre><code>$ docker run -i -t redcricket/react-tutorial:latest /bin/bash
</code></pre>

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

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

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:

<a href="https://i.stack.imgur.com/7nhPY.png" rel="noreferrer"><img src="https://i.stack.imgur.com/7nhPY.png" alt="enter image description here"></a>

That launches this …

<a href="https://i.stack.imgur.com/Aw7J5.png" rel="noreferrer"><img src="https://i.stack.imgur.com/Aw7J5.png" alt="enter image description here"></a>

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

blocks|key|1599659|text|问题在于gitbash，但是对于powershell，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1599660|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|328623|text|发生在我身上。从Git+Bash，在Windows+8上运行Docker工具箱。有两件事正在发生。从git+bash，我们似乎没有完全升级的权限到docker守护进程(即使我使用管理权限运行git+bash+)。因此：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328624|尝试从您的停靠终端运行命令。(给你特权)。|ordered-list-item|328625|要补偿窗口文件夹命名格式中的错误，请不要忘记引用路径。(转义空格和/或大写错误)|328626|发自：|328627|docker+run+-v+$(pwd):/data+image_ref|code-block|syntax|javascript|328628|至：|328629|docker+run+-v+"$(pwd):/data"+image_ref|328630|(请注意$(pwd):/data中后面的引号)。|offset|length|style|CODE|328631|entityMap^0|0|0|0|0|0|0|0|4|C|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|11|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|13|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|14|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|15|8|@]|9|@]|A|$L|M]]|$1|R|3|S|5|6|7|16|8|@$T|17|U|18|V|W]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|Y|$]]

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:
<ol>
<li>Try running the command from your docker terminal. (gives you privilege).
</li>
<li>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
</li>
</ol>
From:
<pre><code>docker run -v $(pwd):/data image_ref
</code></pre>
To:
<pre><code>docker run -v &quot;$(pwd):/data&quot; image_ref
</code></pre>
(notice the enclosing quotes in the latter around <code>$(pwd):/data</code>).

blocks|key|800757|text|只需在cmd开头添加“winpty”，尝试如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|800758|$+winpty+docker.exe+run+--rm+-v+"/c/users/vipul+rao/documents/github/wappalyzer:/opt/wappalyzer"+-it+wappalyzer/dev|code-block|syntax|javascript|800759|为什么会发生这种事？这里有更多详细信息：http://willi.am/blog/2016/08/08/docker-for-windows-interactive-sessions-in-mintty-git-bash/|offset|length|800760|entityMap|0|LINK|mutability|MUTABLE|url|http://willi.am/blog/2016/08/08/docker-for-windows-interactive-sessions-in-mintty-git-bash/^0|0|0|K|2J|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

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

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

Why this happens? More details here:
<a href="http://willi.am/blog/2016/08/08/docker-for-windows-interactive-sessions-in-mintty-git-bash/" rel="nofollow noreferrer">http://willi.am/blog/2016/08/08/docker-for-windows-interactive-sessions-in-mintty-git-bash/</a>

blocks|key|1599631|text|获得运行docker-compose+exec+workspace+bash时的错误|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1599632|所以只需前缀为winpty+winpty+docker-compose+exec+workspace+bash|1599633|entityMap^0|4|Y|0|E|15|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

Got this error for running <code>docker-compose exec workspace bash</code>

So just prefix with winpty <code>winpty docker-compose exec workspace bash</code>

blocks|key|328247|text|这可能是因为您没有在Docker终端中运行命令。如果没有，则可能无法正确连接到Docker守护进程，也无法正确地进行交互。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328248|确保您在实际码头运行命令。|328249|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

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.

blocks|key|328461|text|对于那些在cmder或conemu中使用WSL和运行的用户，我建议不要使用安装在“Program”窗口上的Docker，而是在ubuntu/linux上的WSL中安装Docker。请记住，您不能从WSL内部运行Docker本身，您必须从安装在WSL中的linux客户端连接到运行在windows上的Docker。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328462|在WSL上安装Docker|328463|curl+-fsSL+https://download.docker.com/linux/ubuntu/gpg+%7C+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|code-block|syntax|javascript|328464|运行实际Docker命令的选项是:使用开关-H连接到Docker|328465|docker+-H+localhost:2375+run+-it+-v+/mnt/c/code:/var/app+-w+"/var/app"+centos:7|offset|length|style|CODE|328466|或设置环境变量docker_host。|328467|export+DOCKER_HOST=tcp://localhost:2375|328468|无论哪种方式，您现在都可以交互地连接到正在运行的Docker容器。|328469|entityMap^0|0|0|0|0|0|27|0|0|0|13|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|12|8|@$M|13|N|14|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@$M|17|N|18|O|P]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

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

<pre><code>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
</code></pre>

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

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

Or set the environment variable docker_host

<code>export DOCKER_HOST=tcp://localhost:2375</code>

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

blocks|key|328382|text|您可以尝试使用Cmder工具，它将工作。它不和Gitbash一起工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328383|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|328405|text|除上述解决方案外。如果您收到了这个对接器附件错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|328406|示例：docker+attach+alpine1|offset|length|style|BOLD|CODE|328407|错误：the+input+device+is+not+a+TTY.++If+you+are+using+mintty,+try+prefixing+the+command+with+'winpty'|328408|解决方案：在docker命令之前添加winpty，即winpty附加应该可以工作。|328409|示例：winpty+docker+attach+alpine1|328410|注意：--我在使用windows基础时得到了这个错误，这个解决方案对我有效。|328411|entityMap^0|0|0|2|3|L|0|0|2|3|2O|0|0|4|0|0|2|3|S|0|0|3|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|Y|8|@$D|Z|E|10|F|G]|$D|11|E|12|F|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@$D|14|E|15|F|G]]|9|@]|A|$]]|$1|M|3|N|5|6|7|16|8|@$D|17|E|18|F|G]|$D|19|E|1A|F|H]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|R|$]]

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

example: <code>docker attach alpine1</code>

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

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

example: <code>winpty docker attach alpine1</code>

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

blocks|key|1599671|text|在尝试运行docker-compose+exec命令时，我也犯了同样的错误。在帮助文档docker-compose+exec+--help中，它展示了如何通过将-T添加到命令选项中，以如下方式禁用伪tty分配：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1599672|docker-compose+exec+-T|1599673|在帮助文档中：|1599674|-T+++++Disable+pseudo-tty+allocation.+By+default+docker-compose+exec+allocates+a+TTY.|1599675|entityMap^0|5|J|17|Q|28|2|0|0|M|0|0|0|2D|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|M|$]]

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

<code>docker-compose exec -T</code>

From the help documentation:

<code>-T Disable pseudo-tty allocation. By default docker-compose exec allocates a TTY.</code>

blocks|key|801189|text|如果您使用的是gitbash，则问题是当设置用于与gitbash.设置发射器一起使用的终端仿真器时。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|801190|相反，您可以将模拟器更改为第一个选项，或者使用|801191|在停靠者运行命令之前的winpty命令|801192|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/KDEcC.png^0|X|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

If you are using gitbash the problem is when setting the terminal emulator for for using with Git bash.<a href="https://i.stack.imgur.com/KDEcC.png" rel="nofollow noreferrer">setting the emurator</a>

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

After I run this 
<code>$ docker run --rm -v &quot;/c/users/vipul rao/documents/github/wappalyzer:/opt/wappalyzer&quot; -it wappalyzer/dev</code>
I am getting the following error
<blockquote>
the input device is not a TTY. If you are using mintty, try prefixing the command with 'winpty'
</blockquote>
What should I use here? I am running Docker on Windows 8 in MINGW64.

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在我做完这个之后$ docker run --rm -v "/c/users/vipul rao/documents/github/wappalyzer:/opt/wappalyzer" -it wappalyzer/dev我收到以下错误输入设备不是TTY。如果使用mintty，请在命令前面加上'winpty‘。我在这里该用什么？我在MINGW64的Windows 8上运行Docker。

问窗口上的码头错误:输入设备不是TTY。如果使用mintty，请在命令前面加上'winpty‘。
EN

回答 17

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问窗口上的码头错误:输入设备不是TTY。如果使用mintty，请在命令前面加上'winpty‘。EN

回答 17

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问窗口上的码头错误:输入设备不是TTY。如果使用mintty，请在命令前面加上'winpty‘。
EN