-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
use docker/cli RunExec and RunStart to handle all the interactive/tty/* terminal logic #9258
Conversation
02cb5ac
to
7d20687
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after cleanup of unused functions, conflict resolution and formatting :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I really like this PR 🤩
Just need to fix the linter issues and remove unnecessary method before merging
89a9a70
to
a5373fd
Compare
There's something weird with this one: test gets an empty stdout, while running same command works. I don't get it |
…/* terminal logic Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Does it need something like https://github.com/creack/pty to have a TTY in the test? See, e.g. https://github.com/moby/moby/blob/a6919e12b103aab6eb95a67450b2a487bfec1097/integration-cli/docker_cli_attach_unix_test.go#L27-L35 |
ok, I eventually remembered the initial intent was to restore TTY auto-detection. Went to far into dependent changes :P |
bd0eea6
to
a2ae4fe
Compare
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
What I did
dropped all the interactive run/exec logic by leveraging RunExec/RunStart from docker/cli
Using this battle-tested code will make compose way more robust than our attempts to re-implement all corner cases
tested to confirm we don't resurect #8908