writing to stdin about dockerode HOT 10 CLOSED

Check the "duplex" branch :)
But it needs to be tested.

Basically it uses a duplex stream encapsulating req and res. It was hacked in 5 mins.
Right now it is failling the test suite on image building and creation.

I will probably look into it this weekend, since I also need it for other issue. #2

from dockerode.

cool. Right now I'm going with manual websockets. Unfortunately I can't get
websockets working w/ unix sockets :( but local tcp works great.

On Fri, Oct 18, 2013 at 2:02 PM, Pedro Dias [email protected]:

Check the "duplex" branch :)
But it needs to be tested.

Basically it uses a duplex stream encapsulating req and res. It was hacked
in 5 mins.
Right now it is failling the test suite on image building and creation.

I will probably look into this this weekend, since I also need it for
other issue. #2 #2

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-26625481
.

from dockerode.

Yeah I've the same problem in here with ws and unixsocket.
I've open an issue websockets/ws#236 on their repo about this.

from dockerode.

unfortunately, I think there's a docker issue too:
http://stackoverflow.com/questions/19456237/docker-websocket-attach-using-unix-sockets

On Fri, Oct 18, 2013 at 2:13 PM, Pedro Dias [email protected]:

Yeah I've the same problem in here with ws and unixsocket.
I've open an issue websockets/ws#236https://github.com/einaros/ws/issues/236on their repo about this.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-26626215
.

from dockerode.

Would very much like to be able to do this as well. Could you also provide docks on consuming regular stdout streams? I'm having trouble passing in a duplex stream and getting output.

from dockerode.

stdin attach via remote api is still in a limbo right now, till I figure out how to do it.

Could you detail your second question?

You can easily attach and separate stderr and stdout, example:
container.attach({stream: true, stdout: true, stderr: true, tty: false}, function(err, stream) {
container.modem.demuxStream(stream, process.stdout, process.stderr);
});

from dockerode.

I figured out my issue - I'm a total stream novice, and didn't realize I needed to override stream._write to get any output.

from dockerode.

No problem :)
BTW, Passthrough stream from streams2 is cool for that, since you don't need to override a lot of stuff :)
http://nodejs.org/api/stream.html#stream_class_stream_passthrough

Regarding stdin attach a lot of people is having issues with it via plain remote api.
Via websockets theres the issue you read above.

So right now it's in limbo.

from dockerode.

Fixed in #38

from dockerode.

Awesome!

from dockerode.