From a1f703247a7cd09d818d333aa764baf57aff8af7 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Mon, 8 May 2017 15:33:14 +0200 Subject: [PATCH] fix confusing description of stdout/stdin pipe Signed-off-by: Sebastiaan van Stijn Upstream-commit: c3dff2359dbea4f6f0f001421ddeae4ef76b931f Component: engine --- components/engine/docs/reference/run.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/engine/docs/reference/run.md b/components/engine/docs/reference/run.md index f5deddfec6..532acebad5 100644 --- a/components/engine/docs/reference/run.md +++ b/components/engine/docs/reference/run.md @@ -133,7 +133,7 @@ You can specify to which of the three standard streams (`STDIN`, `STDOUT`, For interactive processes (like a shell), you must use `-i -t` together in order to allocate a tty for the container process. `-i -t` is often written `-it` as you'll see in later examples. Specifying `-t` is forbidden when the client -standard output is redirected or piped, such as in: +is receiving its standard input from a pipe, as in: $ echo test | docker run -i busybox cat