summaryrefslogtreecommitdiff
path: root/test/system
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2021-03-18 06:33:25 -0400
committerDaniel J Walsh <dwalsh@redhat.com>2021-03-24 16:33:30 -0400
commit00949d0bd8a08dcb4d619bebddd1dc3ef3b62e73 (patch)
tree3cc3411a8d46064a41b45aa01c8639807da0714a /test/system
parentaf91f27d85f4104267eea493f8588f8c6a2d01e3 (diff)
downloadpodman-00949d0bd8a08dcb4d619bebddd1dc3ef3b62e73.tar.gz
podman-00949d0bd8a08dcb4d619bebddd1dc3ef3b62e73.tar.bz2
podman-00949d0bd8a08dcb4d619bebddd1dc3ef3b62e73.zip
Check if stdin is a term in --interactive --tty mode
If you are attempting to run a container in interactive mode, and want a --tty, then there must be a terminal in use. Docker exits right away when a user specifies to use a --interactive and --TTY but the stdin is not a tty. Currently podman will pull the image and then fail much later. Podman will continue to run but will print an warning message. Discussion in : https://github.com/containers/podman/issues/8916 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'test/system')
-rw-r--r--test/system/030-run.bats11
1 files changed, 11 insertions, 0 deletions
diff --git a/test/system/030-run.bats b/test/system/030-run.bats
index b2999a9e7..39ade22af 100644
--- a/test/system/030-run.bats
+++ b/test/system/030-run.bats
@@ -668,4 +668,15 @@ json-file | f
is "$output" ".*HOME=/.*"
}
+@test "podman run --tty -i failure with no tty" {
+ run_podman run --tty -i --rm $IMAGE echo hello < /dev/null
+ is "$output" ".*The input device is not a TTY.*"
+
+ run_podman run --tty=false -i --rm $IMAGE echo hello < /dev/null
+ is "$output" "hello"
+
+ run_podman run --tty -i=false --rm $IMAGE echo hello < /dev/null
+ is "$output" "hello"
+}
+
# vim: filetype=sh