Forbid client piping to tty enabled container
Forbid `docker run -t` with a redirected stdin (such as `echo test | docker run -ti busybox cat`). Forbid `docker exec -t` with a redirected stdin. Forbid `docker attach` with a redirect stdin toward a tty enabled container. Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>
This commit is contained in:
committed by
Tibor Vass
parent
acd8287c74
commit
76daef2b9a
@ -94,9 +94,10 @@ specify to which of the three standard streams (`STDIN`, `STDOUT`,
|
||||
|
||||
$ sudo docker run -a stdin -a stdout -i -t ubuntu /bin/bash
|
||||
|
||||
For interactive processes (like a shell) you will typically want a tty
|
||||
as well as persistent standard input (`STDIN`), so you'll use `-i -t`
|
||||
together in most interactive cases.
|
||||
For interactive processes (like a shell), you must use `-i -t` together in
|
||||
order to allocate a tty for the container process. Specifying `-t` is however
|
||||
forbidden when the client standard output is redirected or pipe, such as in:
|
||||
`echo test | docker run -i busybox cat`.
|
||||
|
||||
## Container identification
|
||||
|
||||
|
||||
Reference in New Issue
Block a user