Aravind SV

@ayoyoness: I had recently changed the part of the description which talks about how to start the agent and didn't check whether it was working. :( Either of this should...

Submitted a PR for this (#67). Changed description on DockerHub to show something which works for now.

@agalpin: Are you saying it's working fine now? Or not?

Could be related to #12? Yes, it would be nice to be able to have a proper data container strategy. Does it make sense to provide a data container image,...

@gregorskii - That makes sense. Would you mind submiting a PR to [this file](https://github.com/gocd/api.go.cd/blob/master/source/includes/plugin_settings/_02-show.md.erb), maybe adding a note?

You could try this. As you can see [here](https://github.com/gocd/gocd-docker/blob/master/gocd-server/go-server-start.sh#L5), the startup script runs a file called `/init.sh`, if it is in the container. So, you can mount a file of...

The file won't be around (will be removed), because it is needed only once during the registration between the agent and server. But, the registration should have happened. If so,...

@Matrikss Which version of the plugin and of GoCD server are you using? I wonder if the "Namespace" configuration parameter is supposed to be used for this. I'd assume you'd...

@Matrikss Oops. Nearly forgot to respond. For now, having the two GoCD servers use a different namespace _should_ take care of it. We're considering something like a label to use...

@jblaine So, are you saying that [this documentation](https://docs.gocd.io/current/advanced_usage/pipelines_as_code.html) needs to explicitly call out that the config repo material can be the same as a "normal" material, which has some source...