Error The input device is not a TTY

Question

I am running the following command from my Jenkinsfile  However  I get the error  The input device is not a TTY    docker run -v  PWD  foobar -it cloudfoundry cflinuxfs2  foobar script sh   Is there a way to run the script from the Jenkinsfile without doing interactive mode   I basically have a file called script sh that I would like to run inside the Docker container

User · Answer

For those who struggle with this error and git bash on Windows  just use PowerShell where -it works perfectly

User · Answer

It s not exactly what you are asking  but   The -T key would help people who are using docker-compose exec   docker-compose -f  srv backend bigdata local yml exec -T postgres backup

User · Answer

I know this is not directly answering the question at hand but for anyone that comes upon this question who is using WSL running Docker for windows and cmder or conemu    The trick is not to use Docker which is installed on windows at  mnt c Program Files Docker Docker resources bin docker exe but rather to install the ubuntu linux Docker  It s worth pointing out that you can t run Docker itself from within WSL but you can connect to Docker for windows from the linux Docker client   Install Docker on Linux  sudo apt-get install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https   download docker com linux ubuntu gpg   sudo apt-key add - sudo add-apt-repository  deb  arch amd64  https   download docker com linux ubuntu   lsb release -cs  stable  sudo apt-get update sudo apt-get install docker-ce   Connect to Docker for windows on the port 2375 which needs to be enabled from the settings in docker for windows   docker -H localhost 2375 run -it -v  mnt c code  var app -w   var app  centos 7  Or set the docker host variable which will allow you to omit the -H switch  export DOCKER HOST tcp   localhost 2375  You should now be able to connect interactively with a tty terminal session

User · Answer

winpty works as long as you don t specify volumes to be mounted such as     mountpoint  or    pwd   mountpoint   The best workaround I have found is to use the git-bash plugin inside Visual Code Studio and use the terminal to start and stop containers or docker-compose

User · Answer

Remove the -it from your cli to make it non interactive and remove the TTY  If you don t need either  e g  running your command inside of a Jenkins or cron script  you should do this  Or you can change it to -i if you have input piped into the docker command that doesn t come from a TTY  If you have something like xyz   docker     or docker      lt input in your command line  do this  Or you can change it to -t if you want TTY support but don t have it available on the input device  Do this for apps that check for a TTY to enable color formatting of the output in your logs  or for when you later attach to the container with a proper terminal  Or if you need an interactive terminal and aren t running in a terminal on Linux or MacOS  use a different command line interface  PowerShell is reported to include this support on Windows   What is a TTY  It s a terminal interface that supports escape sequences  moving the cursor around  etc  that comes from the old days of dumb terminals attached to mainframes  Today it is provided by the Linux command terminals and ssh interfaces  See the wikipedia article for more details  To see the difference of running a container with and without a TTY  run a container without one  docker run --rm -i ubuntu bash  From inside that container  install vim with apt-get update  apt-get install vim  Note the lack of a prompt  When running vim against a file  try to move the cursor around within the file

User · Answer

when using  git bash     1  I execute the command   docker exec -it 726fe4999627  bin bash   I have the error   the input device is not a TTY   If you are using mintty  try prefixing the command with  winpty    2  then  I execute the command   winpty docker exec -it 726fe4999627  bin bash   I have another error   OCI runtime exec failed  exec failed  container linux go 344  starting container process caused  exec    D  Git usr bin  bash exe    stat D  Git usr bin bash exe  no such file or directory   unknown   3  third  I execute the   winpty docker exec -it 726fe4999627 bash   it worked   when I using  powershell   all worked well

User · Answer

I believe you need to be in a TTY for docker to be able to allocate a TTY  the -t option   Jenkins executes its jobs not in a TTY   Having said that  the script you are running within Jenkins you may also want to run locally  In that case it can be really convenient to have a TTY allocated so you can send signals like ctrl c when running it locally   To fix this make your script optionally use the -t option  like so    test -t 1  amp  amp  USE TTY  -t   docker run   USE TTY

User · Answer

Using docker-compose exec -T fixed the problem for me via Jenkins docker-compose exec -T containerName php script php

User · Answer

if using windows  try with cmd   for me it works  check if docker is started

User · Answer

My Jenkins pipeline step shown below failed with the same error           steps               echo  Building                   sh  sh   Tools build sh              In my  build sh  script file  docker run  command output this error when it was executed by Jenkins job  However it was working OK when the script ran in the shell terminal The error happened because of -t option passed to docker run command that as I know tries to allocate terminal and  fails if there is no terminal to allocate   In my case I have changed the script to pass -t option only  if a terminal could be detected  Here is the code after changes    DOCKER RUN OPTIONS  -i --rm     Only allocate tty if we detect one if   -t 0    amp  amp    -t 1    then     DOCKER RUN OPTIONS   DOCKER RUN OPTIONS -t  fi  docker run  DOCKER RUN OPTIONS --name my-container-name  my-image-tag

User · Answer

If you are  like me  using git bash on windows  you just need to put      winpty   before your  docker line     winpty docker exec -it some cassandra bash

[docker] Error "The input device is not a TTY"

Examples related to docker

Examples related to jenkins

Examples related to jenkins-pipeline