When run in a docker container, "stty -echo" in say-hello.sh causes problems

[elimisteve]

debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype

Couldn't figure out a solution for this.

[chfoo]

Will getting rid of stty -echo work? Maybe the say-hello.sh could check for a environment variable before doing the virtual machine relevant code.

[elimisteve]

I think the ENV var check is a good idea, though changing every program
that might run in Docker doesn't seem scalable :-).

--Steve
On Sep 6, 2014 9:51 PM, "Christopher Foo" notifications@github.com wrote:

Will getting rid of stty -echo work? Maybe the say-hello.sh could check
for a environment variable before doing the virtual machine relevant code.

—
Reply to this email directly or view it on GitHub
#6 (comment)
.

[chfoo]

Can you do a pull request on ArchiveTeam/warrior-code2 with a variable check? I don't have any time figure out which variable to check and to test the docker instance.