verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
antranigv has quit [Ping timeout: 276 seconds]
antranigv has joined #buildbot
mjw has joined #buildbot
wielaard has joined #buildbot
mjw has quit [Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))]
wielaard is now known as mjw
mark_ has joined #buildbot
<_hc[m]> Anyone have a dead simple example of master/worker using DockerLatentWorker? I have it _almost_ working but I'm baffled. I keep getting this in the master's logs:
<_hc[m]> "
<_hc[m]> "2022-06-23 15:07:58+0000 [-] Timing out client: IPv4Address(type='TCP', host='127.0.0.1', port=35262)
<Zorry> do it get started okey?
<Zorry> config ?
<_hc[m]> When I trigger a build, it does start the container, and I can connect to it via `docker exec`. That's how I got that worker log
<_hc[m]> master/master.cfg - https://clbin.com/t4ZSi
<_hc[m]> master/buildbot.tac - https://clbin.com/MO3A4
<_hc[m]> worker buildbot.tac https://clbin.com/3fik3
<_hc[m]> worker Containerfile - https://clbin.com/aL2HD
<_hc[m]> master is running a docker locally (via podman and _podman-docker-)
<_hc[m]> * master is running a docker locally (via podman and _podman-docker_)
<_hc[m]> s/podman/_podman_/, s/docker-/docker_/
kveremitz has quit [Ping timeout: 260 seconds]
mjw has quit [Quit: Leaving]
<Zorry> set followStartupLogs=True to get more logs
<glogan> This gets templated out via ansible
<glogan> I have three worker hosts (this includes the master), and communicate to all three via their tcp connections
<glogan> the external workers forward their internal ports via ssh tunnels, but you can ignore that bit
<glogan> I suspect the worker container is the issue here
<glogan> let me find mine
<glogan> might be important. I seem to remember running into something like this when I first started
kveremitz has joined #buildbot
<glogan> IIRC, the docker latent spins up and expect something right away. If it doens't get it then it shuts down
mark_ is now known as mjw
<glogan> so the default ubuntu 22.04 docker image fails to apt-get update out of the box
<glogan> because it can't read the keyring files as `_apt`
<glogan> but you can't fix that as far as I can tell, without apt-get-ing something
* glogan bangs head on desk
<glogan> ah, because gnupg isn't installed. At all
<_hc[m]> that sounds like a bug in the docker image
<glogan> oh lordy. No, it's a bug in docker itself. Crap
<glogan> checked on my build nodes -> failure, check on my desktop -> works
<glogan> docker versions are different
felixfontein has quit [Quit: reboot]
felixfontein has joined #buildbot
<_hc[m]> this was one of the bigs that I was missing: `masterFQDN="localhost",`
<_hc[m]> bits
<glogan> got it working at least?
mjw has quit [Quit: Leaving]