Add gitlab-runner to gitlab-development-kit

Debugging an issue on gitlab-ci-multi-runner recently, I had cause to register a locally-built runner against a gdk-supervised GitLab. @ayufan suggested I add the process to the README.md - this issue is for that.

Reassigned to @nick.thomas

@nick.thomas great! I suggest creating a separate markdown file dedicated to the topic in doc/howto , and putting a link to that file in doc/howto/README.md.

Yep, I was very pleased to see the docs reorg MR - well timed!

The main sticking point here is getting the docker (rather than shell) worker running, I've been experimenting a bit and trying to get GDK to generate a gitlab/config/gitlab.yml with host: <an IP docker can use> rather than host: localhost. It needs this (even if the IP is RFC1918) because 127.0.0.1 in the container is different to 127.0.0.1 outside of it.

The documentation mentions a host file (to go with the port file) but I've had no success there yet. Editing gitlab.yml manually works, at least!

@nick.thomas is this about the hostname reported by the application (e.g. in clone links) or about the actual listen address. The 'host' file controls the latter.

If the former matters (because the runner is on a separate machine from where GDK runs?) I would let GDK listen on 0.0.0.0 and manually insert the correct IP in gitlab.yml.

Also you can use ERB in gitlab.yml so if there is some dynamic way to get to the external IP that could work. Ping me on slack if you are stuck on this for too long.

It's the former - GitLab reports the clone URL to gitlab-ci-multi-runner using it, so it needs to be accessible from inside the docker container.

Should have a nice guide for review tomorrow :)

mentioned in merge request !177 (merged)

I would like this also. It could be a simple as a readme sub-page in the gdk docs.

Status changed to closed by commit c3dd36fa