Am 17.12.22 um 08:50 schrieb Piotrek: > On 14.12.2022 23:23, René Scharfe wrote: > >> Curious that only macOS should be affected. Is stdin of a hook script a >> TTY on that platform? Or can "docker compose" handle stdin not being a >> TTY and stdout being one there? > Well, seems like I somehow tested this wrong. Tried it again from > scratch and on linux I also get this error. Ah, OK. > Docker compose CLI options page is a little confusing because of > these: > >>--interactive , -i true Keep STDIN open even if not attached. >>--no-TTY , -T true Disable pseudo-TTY allocation (default: auto-detected). >>--tty , -t true Allocate a pseudo-TTY. > > Second column with `true` values is titled `Default`, whatever it means. > So `--tty` and `--no-TTY` is set by default? Anyway, seems like it is > checking if at least one of stdout, stding, stderr is a tty and then > tries to allocate a tty to all. > > You can check docs here > https://docs.docker.com/engine/reference/commandline/compose_run/#options Yeah, having the last two both on by default seems impossible. Perhaps the text in the parenthesis means that "default" is actually to detect TTYs automatically? In any case the help text could be clearer. > As a final solution I used makefile "magic" with `ifeq` and shell command like this: > > $(shell test -t 0) > ifeq ($(.SHELLSTATUS), 1) > ALLOCATE_TTY = --no-TTY > endif > > docker compose run $(ALLOCATE_TTY) --rm --entrypoint "" app /code/test.sh OK. Would be nice if "docker compose" could handle that case automatically, though, wouldn't it? :) > Maybe I'll just write to to them to clarify documentation on how > those TTY options actually works by default. Good idea. René
