Closed alexjfisher closed 3 years ago
@trevor-vaughan Hi! Any chance you could spare some beaker docker expertise?
Our github workflow has a 'gitlab' service started, but the beaker container doesn't seen to have any network connectivity with it. (Also see this thread)
Feel free to push any commits BTW ;)
I tried to debug this a little bit further. Some things I've learned:
dockeropts
config option. But I don't understand the syntax.voxpupuli/puppet-vault_lookup
" solution (creating a dedicated beaker nodeset) seems to be not an option because we would need to do it for each supported OS.Let's see if I broke it again with my latest change. Feel free to drop that commit if it doesn't.
We shouldn't forget to create issues that we've dropped Amazon Linux and EL6 for the changelog.
I think the next release will have a substantial release summary. I'm hoping to get PR together based on https://github.com/syseleven/puppet-gitlab_ci_runner/tree/clean-move-to-concat-deferred At the moment, the config file is only written when registering a runner, and any subsequent config changes you make have no effect. There are also plenty of more exotic configurations you can't make whilst registering.
For completeness (and mainly because I pinged Trevor and don't want to waste his time!), in https://github.com/voxpupuli/puppet-gitlab_ci_runner/pull/105 I managed to get the docker networking working in the way we originally wanted. Might revisit this at a later date.
We shouldn't forget to create issues that we've dropped Amazon Linux and EL6 for the changelog.
Done via https://github.com/voxpupuli/puppet-gitlab_ci_runner/issues/118
This PR is a continuation of https://github.com/voxpupuli/puppet-gitlab_ci_runner/pull/93 (which I accidentally got into a closed state I couldn't reopen).