-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] docker compose exec/run -i/-t/-T flags are inconsistent with docker exec/run #10228
Comments
|
Maybe we could have an option to opt into consistent behavior instead of having backward compatibility, that we could set in some kind of global configuration file? |
The question then is to know which of With current flags, you can set |
You're only addressing one of the two use cases. |
Are the docker clis really going to maintain backward compatibility forever? |
Description
The inconsistent behavior of
-i
/-t
/-T
flags indocker exec
(/run
) anddocker compose exec
(/run
) is a frustrating cognitive burden.In at least four cases (no flags when stdin is tty; and when stdin is piped: no flags,
-i
flag,-T
flag) the behavior ofdocker exec
/docker compose exec
is inconsistent.Is the inconsistency desirable for any reason? I think they should be completely consistent.
I haven't fully investigated the differences between
docker run
/docker compose run
but I assume they're about the same.Steps To Reproduce
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: