Repository navigation
[BUG] Error when stdin is not a TTY but stdout is a TTY #13228
Description
Activity
the issue is not about allocating a TTY, but about running interactive. While
docker runrequires an explicit--interactiveflag,docker compose rundoesn't: interactive mode is the default mode for legacy reasons. Basically, most users of thedocker runcommand always also pass-itflags, so compose made this the default behavior)You can disable this using
docker compose run --interactive=false ...I understand this behavior now and I can see that it is for legacy reasons. However, I do think docker compose should not error in this reasonable use case, or at least, should print a better message, let the user has some clue about how to fix the problem.
@SmartHypercube The error message isn’t coming from Compose itself, but from the engine, triggered by passing default attributes that lead to this behavior. As @ndeloof mentioned, there’s probably something we can do. I’ll take some time to propose a solution.
Reacted by Hypercube
Description
docker-composewill error with a misleading message when stdin is not a TTY but stdout is a TTY, andstdin_open: true.dockerdoesn't have this problem.Steps To Reproduce
compose.yaml:echo a | docker-compose run --rm main | catYou will get an
aas output.echo a | docker-compose run --rm mainI expect to get an
aas output, becauseecho a | docker run -i --rm debian:trixie catalso outputs ana. But I gotthe input device is not a TTY, which is misleading --- I did not ask for a TTY, why isdocker-composecomplaining the input device not being a TTY? And it's very hard to guess that the actual problem is related to stdout (being a TTY), not stdin.Compose Version
Docker Environment
Anything else?
No response