Skip to content

Documented EOF in ATTACH_CONTAINER_INPUT #340

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.

Sign up for GitHub

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

Merged
vinodkone merged 1 commit into from
Jul 22, 2019
Merged

Documented EOF in ATTACH_CONTAINER_INPUT #340

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion docs/operator-http-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3816,7 +3816,9 @@ they may contain subtypes of either DATA or CONTROL. DATA messages
must be of type STDIN and contain the actual data to stream to the
STDIN of the container being attached to. Currently, the only valid
CONTROL message sends a heartbeat to keep the connection alive. We may
add more CONTROL messages in the future.
add more CONTROL messages in the future. An empty DATA message of type
STDIN indicates EOF. If the container was launched with TTYInfo in their
ContainerInfo, an EOT DATA message is expected instead.

```
ATTACH_CONTAINER_INPUT HTTP Request (JSON):
Expand Down Expand Up @@ -3868,6 +3870,19 @@ Accept: application/json
}
}
}
}215
{
"type": "ATTACH_CONTAINER_INPUT",
"attach_container_input": {
"type": "PROCESS_IO",
"process_io": {
"type": "DATA",
"data": {
"type": "STDIN",
"data": ""
}
}
}
}
...

Expand Down