+Kevin On Wed, May 31, 2017 at 3:31 PM, Brad <[email protected]> wrote:
> Hi all, > > I'm interested in the container attach and exec feature added in version > 1.2.0. > > I'm using the LAUNCH_NESTED_CONTAINER_SESSION and ATTACH_CONTAINER_INPUT > calls on the operator API to launch an embedded container so I can then > stream the stdin and stdout/err back for remote debugging of the parent > process. > > In my tests so far, I can get stdout data back if I run with > setShell(true) and a command info value of: > > "while [ true ]; do echo $(date) hello from nested; sleep 10; done" > > That works fine, I get stdout data packets back every ten seconds as > expected. If I then change the command info value to "bash" with > setShell(false) I don't get any stdout/stderr data back. > > I've looked at what's going over the wire using tcpdump for agent port > 5051 and I can see the stdin data PROCESS_IO packets are being transmitted. > I can also see entries in the mesos agent log which seem to show my API > calls getting processed: > > I0531 21:45:39.704516 9 http.cpp:521] Processing call > LAUNCH_NESTED_CONTAINER_SESSION > > I0531 21:45:39.767571 12 http.cpp:521] Processing call > ATTACH_CONTAINER_INPUT > > I seem to be a but stuck at this point. I'd appreciate any pointers I > could get on where I'm going wrong. > > I'm also slightly concerned I may have misunderstood the purpose of this > feature! Is this a viable use case? > > Thanks, > Brad. >
