01:54 <glogan> Question: I tried to use the dockerfile parameter on the docker latent today. The docs say it can be the string content of the dockerfile, but the worker barfs and the stack trace makes it clear that it's trying to open() a file.

01:54 <glogan> So what's wrong here? Are the docs wrong and it should definitely be a file path?

01:55 <glogan> Or should it accept either?

06:21 <razrdog[m]> https://github.com/buildbot/buildbot/blob/master/master/buildbot/worker/docker.py#L273

06:21 <razrdog[m]> Looks like the code to build it is here. There seems to be logic to render from string content

06:23 <razrdog[m]> Its in an if else where `if custom_context ` then we build from a file. Otherwise we read the string as the dockerfile content.

06:23 <razrdog[m]> Its not clear to me what would set or not set custom context? Is that a variable you set in your config?

12:25 <glogan> That's a flag in the latent config. I'm... Not sure if I had it set to true or false. I know I was playing with it, but I was having other troubles too. Will try with the custom context

19:26 <glogan> hey, there we do, that's working razrdog, ty

19:49 <razrdog[m]> Great! So removing custom context from config got it working?

20:12 <glogan> yep. custom_context=false, dockerfile=somestring

20:12 <glogan> my only issue now seems to be docker login related

20:12 <glogan> in that I'm spinning up latent workers on other nodes, and the login data isn't in the right place(s)