the input device is not a TTY - when running docker-compose exec command on Jenkins

Question

system("docker-compose -p #{ENV['COMPOSE_PROJECT_NAME']} exec #{ENV['BROWSER']} chmod 777 /home/seluser/Downloads")

Running this command from ruby test on Jenkins slave causes error the input device is not a TTY

Locally (on Catalina OS) there's no error.

Analogical docker command works successfully on Jenkins:

system("docker exec \$(docker ps --filter name=#{ENV['BROWSER']}_1 --format {{.ID}}) sudo chmod 777 /home/seluser/Downloads")

What's wrong with docker-compose?

Val Kalinichenko · Accepted Answer · 2020-04-04 20:52:49Z

2

Found solution here https://github.com/docker/compose/issues/5696 Need to add -T' option and rundocker-compose exec -T-T Disable pseudo-tty allocation. By defaultdocker-compose exec` allocates a TTY.

answered Apr 4, 2020 at 20:52

Val Kalinichenko

3513 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

the input device is not a TTY - when running docker-compose exec command on Jenkins

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related