Matías Bellone

I agree with the spirit of this issue, but the amount of scenarios currently covered by the plugin make it quite difficult to make such radical changes to it. We...

> > I have found the issue, though I have the right docker-compose version, my docker version is 18.06, where at least 18.09 is needed. > > where do you...

After reading and re-reading the description of this issue, the logs and related links, my understanding indicates that this was an issue with the agent that can be solved, [as...

@patrobinson, first and foremost sorry for the delay in getting back to you. Hope that you have continued to use the plugin since and found the improvements and fixes made...

My opinion has always been: _security by default_, that way you would have to (ideally) read the documentation, understand the risks and **opt-in** to a less secure execution. Realistically, though,...

I was able to reproduce this issue quite reliably. The trick is to do so on a pristine agent that has never talked to github before. The setup of the...

Hi @TSMMark! As far as I understand, the added script is ran in the background and waits for the main container (`${run_container}`) to be up and running before doing a...

As #258 was closed, I created PR #276 to implement this :)

This is extremely strange and not something I have experienced or seen before. The most likely explanation I can think of is that `compose` is not recognized as a valid...

Instead of using the `username` plugin option, couldn't the pipeline or hook set the variable `BUILDKITE_PLUGIN_DOCKER_LOGIN_USERNAME` directly? I don't see why that wouldn't work