New state of 'nil' is invalid, when sending byte 0x90 followed by any other to stdio

[averri]

Consider the following commands:

docker run centos printf '\x90\x00'
docker run centos echo ┐

Running any of that commands on Docker toolbox on Windows 7 (MINGW terminal) will print:

New state of 'nil' is invalid.

I have discovered that the byte 0x90 followed by any other will cause the problem.

If running just printf '\x90\x00' inside the container, the shell will exit and the same message will be printed. The problem does not occur when running on Docker on Linux.

The char ┐ correspond to the UTF-8 0xE2 0x94 0x90, so in the command echo ┐, the complete sequence is 0xE2 0x94 0x90 0x0A, again, the 0x90 followed by another byte.

[duthng]

@averri how would we fix this?

[geosava]

Hello everyone

As I have wrote here : jhipster/generator-jhipster#5950
I am facing the same issue in windows 10 and the latest Docker for Windows CE.
As I understand it is a problem with docker's terminal emulation on windows.
Is there a know solution to overcome this problem on windows systems?
As I read here moby/moby#22480 a solution would be to install SSHd in the docker container to access it through ssh and not docker terminal.
Can anyone validate this is a working solution?

Thanks.

[DHager]

Ran into the same issue on Windows 7 with Docker Quickstart Terminal, docker version 1.12.2. Thanks @averri for the super-easy repro step.

Off-topic: In my case it was from some PHP code in symfony/flex (which I'll open a separate issue for) that attempts to print out a message about adding a star on github, and uses the symbol:

U+2B50 | ⭐ | \xe2\xad\x90 | WHITE MEDIUM STAR

[keegancsmith]

This is affecting Sourcegraph as well. We print a logo in the console on startup, but docker toolbox is crashing. https://github.com/sourcegraph/sourcegraph/issues/398

[boly38]

I was able to reproduce with non latin chars like this russian word французских.

If I workaround this by dropping \x90, then data is also corrupted (my example became -’)
BTW docker console doesn't crash.

My 2 cents

[rfaelens]

This is affecting Docker build of R packages, as testthat uses unicode symbols by default to report progress.

[javagl]

For those looking for the Wisdom of the Ancients here: In some cases, a workaround can be to route the output into the void and back, as in

yourCommandThatPrintsSomething | cat

so that some output appears at the console.

Doing a

yourCommandThatPrintsSomething >/dev/null

swallows the output completely, preventing the shutdown at least. With

yourCommandThatPrintsSomething > output.txt

you might also be able to keep output.txt open in a text editor and use this text editor as some sort of console. Ouch.