[Buildbot-devel] buildbot, docker, and the slave protocol

[Dan Kegel]

Probably it's not docker's fault; I just verified that
 sudo apt-get install lxc-docker
 sudo docker run -i -t ubuntu /bin/bash
didn't disturb ssh or netcat connections.
So I'm off debugging our own stuff, but still,
a stateless protocol that could tolerate disconnections
might be handy.

On Wed, Jan 28, 2015 at 7:26 PM, Dan Kegel <dank at kegel.com> wrote:
> I'm trying to use docker inside a build run via buildbot.
> (Not the other way around... this is a normal buildbot, no containers,
> no nothing.)
>
> The slave runs a shell step that builds a docker image
> and intends to use it to run tests, but the job fails with messages like
> remoteFailed: [Failure instance: Traceback (failure with no frames):
> <class 'twisted.internet.error.ConnectionLost'>: Connection to the
> other side was lost in a non-clean fashion.
> ]
>
> This just happened, so I haven't really looked into it yet, but it kind
> of feels like Docker is frobbing the network and making buildbot's
> connection drop.   Shame buildbot doesn't have a stateless client protocol
> lying around waiting for someone to test it.  (Does it?)
> - Dan