<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Pierre,<br>
</p>
<div class="moz-cite-prefix">On 2019-03-13 6:44 a.m., Pierre Tardy
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ+soVdAeZ2E7qG7Ufb+q98p6ob=YiSNYZ7uFq4XWpZbibjXtA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi,
<div><br>
</div>
<div>You can look at the docker logs of the worker to try and
find out why they did exit early.</div>
<div>If the steps are created, this means that there has been at
least a bit of activity.</div>
<div>This is weird, as usually once you manage to get the latent
worker connected, you passed the biggest difficulty.</div>
</div>
</blockquote>
<p>Right. :-)</p>
<p>So, I have managed to resolve my problems, so I'd like to report
back my findings, for the record.</p>
<p>The main issue was my own confusion about how DockerLatentWorker
actually operate. Having successfully built my project with
`bbtravis run`, I expected the basic mechanism to be the same,
i.e. a Worker "shell" to push commands into a docker instance.
What I had failed to realize was that a buildbot worker instance
actually had to run *inside* the container.</p>
<p>After that clarification, and having rebuilt my docker image
correspondingly, things started to fall into place (I could
inspect the logs from the container to see the debug).</p>
<p>The next stumbling block was the setting up of the communication
between master and worker. With some help from IRC I was able to
rewrite the `buildbot.tac` worker code to fetch master name,
password, as well as some other variables from the environment,
which the DockerLatentWorker conveniently prepared.</p>
<p>The last item was / is how to establish the master host address
such that the worker can reach it from inside the container. Given
that the master passes the hostname down to the worker, and given
that in my case I was running the worker on the same machine, I
simply added `--network host` to the worker's `host_config`
constructor argument, and things started to work. Still, this
seems a bit hackish at best. Any idea how to do that properly ?</p>
<p>I still think one or two example setups would be nice, as a
starting point. So far all I have found were exampes using a
LocalWorker, or (in case of the buildbot metabot), a
KubeLatentWorker, which is one step too much.<br>
</p>
<p><br>
</p>
<p>Thanks,<br>
</p>
<p><br>
</p>
<div class="moz-signature">
<div class="moz-signature"><img moz-do-not-send="false"
src="cid:part1.1E54C880.00F555B9@seefeld.name" alt="Stefan"
width="73" height="45"><br>
<pre>--
...ich hab' noch einen Koffer in Berlin...
</pre>
</div>
</div>
</body>
</html>