The runners that register with gitlab server is automatically enging up in "lock".

Adding the capability to register as "locked/unlocked" is easy and possible to implement with little effort.

Introduce a config variable to use in the register command (action and event)

hej Erik,

I am starting to trial the gitlab-runner charm.. but it seems I've hit the first snag.. I wanted to use Docker but am running within LXD.. can I use docker images within LXD or .. I guess whatever I need to setup to run should already be present in the same machine ? If I just want to use docker images do I .. back the charm for k8s usage and spin it up on minik8s?

Running with gitlab-runner 14.9.1 ()
  on juju-1.lxd 
Preparing the "docker" executor
Using Docker executor with image registry.gitlab.com/jrgemcp-public/gitlab-cicd-docker/build-conan-docker:latest ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image registry.gitlab.com/jrgemcp-public/gitlab-cicd-docker/build-conan-docker:latest ...
Using docker image sha256:232827d262f12ccc14ba7d4fb14b611e80e57df059d61854366054cdd3ff9dc8 for registry.gitlab.com/jrgemcp-public/gitlab-cicd-docker/build-conan-docker:latest with digest registry.gitlab.com/jrgemcp-public/gitlab-cicd-docker/build-conan-docker@sha256:93fbdb226fa193b765ea350578850b8955a2dc6103ad8bb26c9c3294e5dd7078 ...
Preparing environment
Running on runner-concurrent-0 via juju-1...
Getting source from Git repository
Fetching changes with git depth set to 50...
Initialized empty Git repository in /builds/some_project/.git/
Created fresh repository.
Checking out ffffff as main...
Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:232827d262f12ccc14ba7d4fb14b611e80e57df059d61854366054cdd3ff9dc8 for registry.gitlab.com/jrgemcp-public/gitlab-cicd-docker/build-conan-docker:latest with digest registry.gitlab.com/jrgemcp-public/gitlab-cicd-docker/build-conan-docker@sha256:93fbdb226fa193b765ea350578850b8955a2dc6103ad8bb26c9c3294e5dd7078 ...
Cleaning up project directory and file based variables
ERROR: Job failed (system failure): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (docker.go:654:120s)

The variable check-interval is not set when spawning a new GitLab runner correctly.

The default is 3 but the config.toml file still says 0

Currently, this charm throws a lot of exceptions but they are not handled.

Mostly thrown is when it is unconfigured and newly started.

maybe the raise usage should be removed and put charm into an error state.

Hello,

I'm experiencing issues with registering runners through this charm. I'm currently deploying a GitLab Server via Juju on Focal.

I'm deploying the runner with the following command:

juju deploy gitlab-runner --config my-config.yaml --series focal

I'm getting the following error message:

WARNING unit.gitlab-runner-one-docker/0.config-changed logger.go:60 FATAL: flag provided but not defined: -template-config

From within the charm I can run the gitlab-runner register command successfully, however it seems that the charm version it is using the flag --template-config which is only available from runner v. 12.2. The latest gitlab-runner version in focal seems to be 11.2 (which is currently installed in my VM).
To confirm this, I've run the command to be registered with the above-mentioned flag and got the failure.
I can see that flag being set here, but the gitlab-runner version required to run that is not available on focal via apt as shown also here.

Is there any way to address this issue?

Thanks in advance for the support,
Best,
Giuseppe

Hello:

This link
https://gitlab.com/gitlab-org/gitlab-runner/blob/master/docs/install/linux-repository.md

Return:

404
Page Not Found
Make sure the address is correct and the page hasn't moved.

Please contact your GitLab administrator if you think this is a mistake.

as i CI admin i want to easily list/remove/add LXD remotes

DOD
juju actions are added to register/list/remove LXD remotes and when registering choose public or private

Currently, the runner doesn't honor the docker-image variable to set it into its configuration when running LXD.

To be able to use docker-in-docker / "dind", you might need to mount docker.sock inside the container that is being run.
Currently there is no automated way of changing this, and you will have to ssh into the gitlab-runner and edit the config.toml file and add this under volume var/run/docker.sock:/var/run/docker.sock
Also, to be able to read and save reports as artifacts when using GitLab CodeQuality with CodeClimate, you might need to mount "/builds:/builds" as well.
This leads to 1 or 2 feature requests:

• be able to add/configure volume mounts in the config.toml using JUJU
• configure for dind: get the automated docker.sock mount automatically

Thank you! :)

when the charm is re-registered it doesn't change to the config value set in the charm config.