Forced -T option for exec and run

[MarcusElevait]

Is there a reason, why the -T option for exec and run commands is always automatically added always? Shouldn't this be up to the user?

[AlexZeitler]

@MarcusElevait In the past, this option has been required to make this library work.

Local tests for the v2 version work for me without -T option.

#275 will validate it works in CI.

[AlexZeitler]

Seems to work on macOS (Intel based), too.

[MarcusElevait]

Thanks for the fast reply.
Yesterday i had the problem, that i could not do something like this:
compose.exec('graphdb', 'bash -c "/init/scripts/reset-data.sh | console --serverURL http://localhost:7200"', dockerComposeOptions)
Which runs perfectly fine, if i do it like that in the terminal
docker compose exec graphdb bash -c '/init/scripts/reset-data.sh | console --serverURL http://localhost:7200'

And my guess is, that it is because of the -T option.

[AlexZeitler]

Looks similar to this one: #116 (comment)

[MarcusElevait]

If i do it like that, it just ignores the pipe and everthing after. It just executes the reset-data.sh file.

[AlexZeitler]

This?

compose.exec('graphdb', ['bash', '-c', '/init/scripts/reset-data.sh | console --serverURL http://localhost:7200'],...)

[MarcusElevait]

This works perfectly fine, thank you very much for your help, appreciate it :-)

[AlexZeitler]

👍