blocks|key|12517|text|运行docker+exec+-i而不是docker+exec+-it解决了我的问题。实际上，我的脚本是由CRONTAB启动的，它不是一个终端。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|12518|提醒一下：|12519|Usage:+docker+exec+[OPTIONS]+CONTAINER+COMMAND+[ARG...]

Run+a+command+in+a+running+container

++-i,+--interactive=false++++Keep+STDIN+open+even+if+not+attached++
++-t,+--tty=false++++++++++++Allocate+a+pseudo-TTY|code-block|syntax|javascript|12520|entityMap^0|2|E|J|F|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

Running <code>docker exec -i</code> instead of <code>docker exec -it</code> fixed my issue. Indeed, my script was launched by CRONTAB which isn't a terminal.

As a reminder: 

<pre><code>Usage: docker exec [OPTIONS] CONTAINER COMMAND [ARG...]

Run a command in a running container

 -i, --interactive=false Keep STDIN open even if not attached 
 -t, --tty=false Allocate a pseudo-TTY
</code></pre>

blocks|key|4520185|text|如果您在Windows上使用docker-machine，并且使用的是GIT+Bash或Cygwin，要“进入”一个正在运行的容器，您需要执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4520186|ssh到虚拟机的docker-machine+ssh+default+(很可能是Virtualbox)|offset|length|style|CODE|4520187|docker+exec+-it+<container>+bash进入容器。|4520188|编辑：|4520189|我最近发现，如果你使用Windows，你可以直接将PowerShell停靠到容器中，使用Cygwin或Git+Bash，你可以使用winpty+docker+exec+-it+<container>+bash，跳过上面的docker-machine+ssh步骤。|4520190|entityMap^0|0|8|Q|0|0|W|0|0|1T|13|32|I|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@$D|Y|E|Z|F|G]|$D|10|E|11|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|O|$]]

If you're on Windows and using docker-machine and you're using GIT Bash or Cygwin, to "get inside" a running container you'll need to do the following:

<code>docker-machine ssh default</code> to ssh into the virtual machine (Virtualbox most likely)

<code>docker exec -it &lt;container&gt; bash</code> to get into the container.

EDIT:

I've recently discovered that if you use Windows PowerShell you can docker exec directly into the container, with Cygwin or Git Bash you can use <code>winpty docker exec -it &lt;container&gt; bash</code> and skip the <code>docker-machine ssh</code> step above.

blocks|key|12536|text|在使用boot2docker的windows上，我收到以下命令的“无法在非tty输入上启用tty模式”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|12537|docker+exec+-it+<containerIdOrName>+bash|code-block|syntax|javascript|12538|下面的命令解决了这个问题|12539|winpty+docker+exec+-it+<containerIdOrName>+bash|12540|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I get "cannot enable tty mode on non tty input" for the following command on windows with boot2docker

<pre><code>docker exec -it &lt;containerIdOrName&gt; bash
</code></pre>

Below command fixed the problem 

<pre><code>winpty docker exec -it &lt;containerIdOrName&gt; bash
</code></pre>

blocks|key|12480|text|docker+exec运行一个新命令in+an+already-running+container。这不是启动新容器的方式--为此使用docker+run。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|12481|这可能是“非tty输入”错误的原因。或者它可能是你运行docker的地方。它是一个真正的终端吗？也就是说，是否有完整的tty会话可用？您可能需要检查您是否处于与的交互会话中|12482|[[+$-+==+*i*+]]+&&+echo+'Interactive'+%7C%7C+echo+'Not+interactive'|code-block|syntax|javascript|12483|来自https://unix.stackexchange.com/questions/26676/how-to-check-if-a-shell-is-login-interactive-batch|12484|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/reference/commandline/cli/#exec|1|https://unix.stackexchange.com/questions/26676/how-to-check-if-a-shell-is-login-interactive-batch^0|0|B|1V|A|I|V|0|0|0|0|2|2P|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|17|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|O|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

<code>docker exec</code> runs a new command <a href="https://docs.docker.com/reference/commandline/cli/#exec" rel="nofollow noreferrer">in an already-running container</a>. It is not the way to start a new container -- use <code>docker run</code> for that.

That may be the cause for the "non tty input" error. Or it could be where you are running docker. Is it a true terminal? That is, is a full tty session available? You might want to check if you are in an interactive session with

<pre><code>[[ $- == *i* ]] &amp;&amp; echo 'Interactive' || echo 'Not interactive'
</code></pre>

from <a href="https://unix.stackexchange.com/questions/26676/how-to-check-if-a-shell-is-login-interactive-batch">https://unix.stackexchange.com/questions/26676/how-to-check-if-a-shell-is-login-interactive-batch</a>

blocks|key|12602|text|我在64位Windows+7中使用Git+for+Windows附带的Mintty时遇到了同样的错误信息。$docker+run+-i+-t+ubuntu+/bin/bash++cannot+enable+tty+mode+on+non+tty+input|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|12603|按照其他答案的建议，我尝试在上面的命令前面加上winpty，但是运行它会显示下面的另一个错误消息：$+winpty+docker+run+-i+-t+ubuntu+/bin/bash+exec:+"D:\\Git\\usr\\bin\\bash":+executable+file+not+found+in+$PATH+docker:+Error+response+from+daemon:+Container+command+not+found+or+does+not+exist..|12604|然后我碰巧运行了下面的命令，它给了我想要的：$+winpty+docker+run+-i+-t+ubuntu+bash+root@512997713d49:/#+ls+bin+++dev++home++lib64++mnt++proc++run+++srv++tmp++var+boot++etc++lib+++media++opt++root++sbin++sys++usr+root@512997713d49:/#|12605|entityMap^0|1H|23|0|1D|5E|0|M|57|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

I encountered this same error message in Windows 7 64bit using Mintty shipped with Git for Windows. 
<code>
$docker run -i -t ubuntu /bin/bash
 cannot enable tty mode on non tty input
</code>

I tried to prefix the above command with winpty as other answers suggested but running it showed me another error message below:
<code>
$ winpty docker run -i -t ubuntu /bin/bash
exec: "D:\\Git\\usr\\bin\\bash": executable file not found in $PATH
docker: Error response from daemon: Container command not found or does not exist..
</code>

Then I happened to run the following command which gave me what I want:
<code>
$ winpty docker run -i -t ubuntu bash
root@512997713d49:/# ls
bin dev home lib64 mnt proc run srv tmp var
boot etc lib media opt root sbin sys usr
root@512997713d49:/#
</code>

blocks|key|12639|text|我在jenkins+job下运行docker+exec+-it，得到错误‘无法在非tty输入上启用tty模式’。不会返回docker+exec命令的输出。我的作业登录顺序是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|12640|jenkins+shell+->+ssh+user@<testdriver>+->+ssh+root@<sut>+->+su+-+<user>+->+docker+exec+-it+<container>|code-block|syntax|javascript|12641|我在jenkins的初始ssh中更改为使用-T标志。"-T+-禁用伪终端分配“。并在docker+exec中使用-i标志，而不是-it。"-i+-交互式。-t+-分配伪tty。“这似乎解决了我的问题。|12642|jenkins+shell+->+ssh+-T+user@<testdriver>+->+ssh+root@<sut>+->+su+-+<user>+->+docker+exec+-i+<container>|12643|行为类型符合这个docker+exec+tty+bug：https://github.com/docker/docker/issues/8755。对docker+bug讨论的解决方法建议使用以下代码：|offset|length|12644|docker+exec+-it+<CONTAINER>+script+-qc+<COMMAND>|12645|使用这种变通方法并没有解决我的问题。不过这很有趣。尝试使用不同的标志，在不同的ssh调用下，您可以看到'not+a+tty‘，即使使用带有docker+exec的-t：|12646|$+docker+exec+-it+<CONTAINER>+script+-qc+'tty'
/dev/pts/0
$+docker+exec+-it+<CONTAINER>+'tty'++++++++++++
not+a+tty
$+docker+exec+-it+<CONTAINER>+bash+-c+'tty'+
not+a+tty|12647|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/docker/docker/issues/8755^0|0|0|0|0|S|18|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|16|8|@]|9|@$M|17|N|18|1|19]]|A|$]]|$1|O|3|P|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

I'm running docker exec -it under jenkins jobs and getting error 'cannot enable tty mode on non tty input'. No output to docker exec command is returned. My job login sequence was:

<pre><code>jenkins shell -&gt; ssh user@&lt;testdriver&gt; -&gt; ssh root@&lt;sut&gt; -&gt; su - &lt;user&gt; -&gt; docker exec -it &lt;container&gt;
</code></pre>

I made a change to use -T flag in the initial ssh from jenkins. "-T - Disable pseudo-terminal allocation". And use -i flag with docker exec instead of -it. "-i - interactive. -t - allocate pseudo tty.". This seems to have solved my problem.

<pre><code>jenkins shell -&gt; ssh -T user@&lt;testdriver&gt; -&gt; ssh root@&lt;sut&gt; -&gt; su - &lt;user&gt; -&gt; docker exec -i &lt;container&gt;
</code></pre>

Behaviour kindof matches this docker exec tty bug: <a href="https://github.com/docker/docker/issues/8755" rel="nofollow">https://github.com/docker/docker/issues/8755</a>. Workaround on that docker bug discussion suggests using this:

<pre><code>docker exec -it &lt;CONTAINER&gt; script -qc &lt;COMMAND&gt;
</code></pre>

Using that workaround didn't solve my problem. It is interesting though. Try these using different flags and under different ssh invocations, you can see 'not a tty' even with using -t with docker exec:

<pre><code>$ docker exec -it &lt;CONTAINER&gt; script -qc 'tty'
/dev/pts/0
$ docker exec -it &lt;CONTAINER&gt; 'tty' 
not a tty
$ docker exec -it &lt;CONTAINER&gt; bash -c 'tty' 
not a tty
</code></pre>

<code>docker exec -it</code> command returns following error "cannot enable tty mode on non tty input" 

<pre><code>level="fatal" msg="cannot enable tty mode on non tty input" 
</code></pre>

I am running docker(1.4.1) on centos box 6.6.
I am trying to execute the following command
<code>docker exec -it containerName /bin/bash</code>
but I am getting following error 

<pre><code>level="fatal" msg="cannot enable tty mode on non tty input" 
</code></pre>

docker exec -it returns "cannot enable tty mode on non tty input"

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

docker exec -it命令返回以下错误：“无法在非tty输入上启用tty模式”level="fatal" msg="cannot enable tty mode on non tty input" 我在centos box 6.6上运行docker(1.4.1)。我正在尝试执行下面的命令docker exec -it containerName /bin/bash，但是我得到了以下错误le

问docker exec -it返回“无法在非tty输入上启用tty模式”
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问docker exec -it返回“无法在非tty输入上启用tty模式”EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问docker exec -it返回“无法在非tty输入上启用tty模式”
EN