The following pull request was submitted through Github. It can be accessed and reviewed at: https://github.com/lxc/lxd/pull/6681
This e-mail was sent by the LXC bot, direct replies will not reach the author unless they happen to be subscribed to this list. === Description (from pull-request) === At least for me, it wasn't clear that one websocket connection per file descriptor was needed to run the command.
From d9ffcd56683646ddb151cef15e6895471d2b3a84 Mon Sep 17 00:00:00 2001 From: Julien Reichardt <g...@jrei.ch> Date: Thu, 9 Jan 2020 16:16:23 +0100 Subject: [PATCH] Improve websocket doc in container exec --- doc/rest-api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/rest-api.md b/doc/rest-api.md index 9189d3936e..b9ac07a126 100644 --- a/doc/rest-api.md +++ b/doc/rest-api.md @@ -914,8 +914,8 @@ Input (run bash): ``` `wait-for-websocket` indicates whether the operation should block and wait for -a websocket connection to start (so that users can pass stdin and read -stdout), or start immediately. +a websocket connection to start for all the available file descriptors (except `control`, which is optional), or start immediately. +This gives the possibility to pass stdin inputs and read stdout/stderr outputs as bytes. If starting immediately, /dev/null will be used for stdin, stdout and stderr. That's unless record-output is set to true, in which case,
_______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel