Attaching tty

[raphink]

Is it possible to attach a tty to jobs started with jobber?

We're using jobber to start containers (using conplicity) and this requires a tty.

[dshearer]

No, at this time that's not possible. Would you need to be able to interact with the tty?

On Apr 18, 2016, at 1:05 AM, Raphaël Pinson notifications@github.com wrote:

Is it possible to attach a tty to jobs started with jobber?

We're using jobber to start containers (using conplicity) and this requires a tty.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

[raphink]

Thank you for your answer. fsouza/go-dockerclient#509 (comment) seems to indicate that I might not need it after all (hopefully I don't need it).

[nicodmf]

In a docker environnement, I have command to launch in a sibling container. Without tty, they don't stop on target container properly after timeout. For the moment i use expect in a child script to simulate tty and permit to keep control on the final command. But this is surelly not the best way, as stderror is encapsulate and a proxy script is mandatory. In this case, the access to a tty, or a virtual tty seems to me the best way.

Description of the environnement :

• Application container
• Task container (with "privileged" configuration)

The task container should launch a script in the application container with :

• docker exec -it appContainer command.

Actually encapasulte in the expect script this is:

• withExpectScript $(timeout) docker exec -it appContainer command

If i remove the -t, the timeout doesn't stop the command in the application container (which is very long to run : >15 minutes).

@dshearer : the terminal could be emulated now ? or have you a better configuration to indicate to me in this case ?