01:37 <razrdog[m]> <glogan> "For example, what the heck..." <- I agree. That's certainly not intuitive

01:39 <razrdog[m]> <glogan> "I'm wondering if it doesn't *..." <- I'm not an expert on anything docker related. But I can take some guesses. So custom context is you providing a file or something to be copied into the docker at build time?

14:58 <glogan> When building a docker image, you have a root directory from which all reference have to be made. This is the same directory as the 'Dockerfile'.

14:58 <glogan> with custom_context == False, looking at the code the docker client is being fed a .read() of an object being built in memory

14:58 <glogan> which, like, cool. But what's the CWD of the build? :)

14:59 <glogan> I guess that's what I'm actually asking. I've tried the master's home dir, the config dir, nothing seems to work

14:59 <glogan> this is complicated by these builds occurring on remote docker instances on other machines

16:54 <razrdog[m]> I'm looking at it and it looks like you do need to be able to provide custom context. I'm not sure why that's the selector for using inline docker files or not. Seems like a bad test.

16:57 <razrdog[m]> So this would be a bug in the latent docker implementation where we want to select based on something other can custom context existing. I imagine its probably pretty easy to tell if something is a file path or a string containing a dockerfile and we should do the if else based on that.

16:57 <razrdog[m]> I suppose by default the path would be . so wherever the docker daemon is being executed from on your remote machine may be where the build is occurring.

17:00 <razrdog[m]> Perhaps looking at /proc/<pid>/cwd on the docker machine. Replacing pid with the paid of the docker daemon. That should be a symlink to the cwd used by docker and is "maybe" where the build is occurring.

17:09 <glogan> doesn't seem to be the right place

17:09 <glogan> tried the worker's path when viewed from both inside and outside the container, on both machines

17:09 <glogan> oh. hell. I wonder

17:09 <glogan> So, the master is also a docker container

17:10 <glogan> wanna bet the fileneeds to be in the master's internal context path?

17:16 <glogan> nope, that doesn't work either

17:28 <glogan> not inside the master's root, the buildbot venv root, or the config root

19:38 <dottedmag> Does anyone know the API endpoint to create a buildset? https://docs.buildbot.net/latest/developer/raml/buildset.html is not helpful, all it says is cryptic "All update methods are available as attributes of master.data.updates"

19:38 <dottedmag> POST-ing to /buildsets does not seem to work either