大网数据广告活动
服务器运维问答

What does "the input device is not a TTY" exactly mean in "docker run" output?

· 52CE 我爱测

This is a command that works: $ echo 'hi there' | docker run -i ubuntu cat hi there This is a command that responds with an error message: $ echo 'hi there' | docker run -it ubuntu cat the input device is not a TTY I would like t…

问题原文

原帖链接 · Mikhail Vasin · CC BY-SA 3.0

This is a command that works:

$ echo 'hi there' | docker run -i ubuntu cat
hi there

This is a command that responds with an error message:

$ echo 'hi there' | docker run -it ubuntu cat
the input device is not a TTY

I would like to figure out exactly what happens here. Not just "remove -t and it'll be fixed".

I know that docker run's -t option stands for "Allocate a pseudo-TTY", and I have read historical overviews of what TTY stands for, but it didn't help me understand what kind of a contract is violated here.

已采纳解答

原帖链接 · Mikhail Vasin · CC BY-SA 3.0

This answer helped me to wrap my head around:

  • by default (without neither -i nor -t options) a Docker container only sends its output to STDOUT,
  • with -i option comes connection to STDIN,
  • -t option pulls in a terminal interface driver, that works on top of STDIN/STDOUT. And when a terminal driver is pulled in, the communication with a container must conform to the terminal interface protocol. Piping a string does not.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2018-02-19)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。