Needs a rebase, @ulyssessouza

strictly speaking, we should handle --interactive=false and not just make this flag a No-Op, but I guess that's a corner

Yes, would be good to support that as well; also (from #9207 (comment)) probably produce an error when passing both -t or -i and -T (conflicting options)

Already added support for --interactive=false on https://github.com/docker/compose/blob/v2/cmd/compose/run.go#L223
Support for combinations of --tty=false and --no-tty is a bit more complex, will look into this on my spare time :)

Yes, that one is more tricky; if the options do not "conflict", we could accept them, but if they "conflict", it's more tricky to define the behaviour (which one should take precedence??). In such cases, I usually make that an error-condition; the advantage with that is that you're sure nobody is able to use the combination (as it errors), which leaves the ability to "allow" the combination in future (if there's a decision on what the expected outcome is).

indeed. I planned to rely on flags.Changed to check is tty is true because this is default or user explicitly user -t, so that we can detect conflict with -T