Is there a way to customise the schedule of the Container Registry Cleanup job?
For context, we use the Docker Registry HTTP API to create a new tag for an existing image without having to pull and push the image.
This morning an image that was tagged in this way disappeared mysteriously from the registry, and it was at about the same time that the Cleanup job ran.
This might be a bug with the cleanup job, but I'm not sure how to give you a reproducible bug report if I can't control when the job runs! (and also if I can ensure the job runs during the night, it won't be a problem anymore)
gitlab.rbvariables via environment variables from the host? So let's say, I define a
ROOT_PASSWORD=fooon the host system, now in the docker-compose I would like to use that env var so its value is used for gitlab_rails['initial_root_password']. This is defined in: https://docs.docker.com/compose/environment-variables/#pass-environment-variables-to-containers
GITLAB_OMNIBUS_CONFIGas this is a multiline string. Tried the following, but without success. The root password was not set, instead I had to lookup and use the generated initial_root_password file.
version: '3.6' services: web: image: 'my-registry/dh/gitlab/gitlab-ee:15.0.3-ee.0' restart: always hostname: 'gitlab.example.com' environment: SMTP_PASSWORD: ROOT_PASSWORD: GITLAB_OMNIBUS_CONFIG: | external_url 'https://gitlab.my-domain.com' ... gitlab_rails['smtp_password'] = ENV['SMTP_PASSWORD'] gitlab_rails['initial_root_password'] = ENV['ROOT_PASSWORD'] ...
hello, I have an issue with submodules and gitlab-runner.
I have a project with submodules, and recursive submodules, like:
This project runs CI since few month, without any issue. but today, I want to remove top/sub-b/subsub-a. and I get this error during repo intialization in CI:
fatal: No url found for submodule path 'top/sub-b/subsub-a' in .gitmodules fatal: run_command returned non-zero status while recursing in the nested submodules of top/sub-b
Initially, GIT_STRATEGY is set to fetch. If I set GIT_STRATEGY to clone, it fixes the issue for this particular runner. But I have several runners, and I can't force the choice of the runner.
gitlabUrl: "https://gitlab.foo.fr/" imagePullPolicy: IfNotPresent unregisterRunners: true concurrent: 2 checkInterval: 10 ## Configure integrated Prometheus metrics exporter ## ref: https://docs.gitlab.com/runner/monitoring/#configuration-of-the-metrics-http-server metrics: enabled: true service: enabled: true serviceMonitor: enabled: true ## Configuration for the Pods that that the runner launches for each new job ## runners: ## Default container image to use for builds when none is specified ## image: rockylinux:8.5 privileged: true tags: "privileged,large" runUntagged: false ## Configure environment variables that will be injected to the pods that are created while ## the build is running. These variables are passed as parameters, i.e. , ## to command. ## ## Note that (see below) are only present in the runner pod, not the pods that are ## created for each build. ## ## ref: https://docs.gexport NAMESPACE="gitlab"itlab.com/runner/commands/#gitlab-runner-register ## env: HOME: /tmp config: | [[runners]] [runners.kubernetes] privileged = true # build container cpu_limit = "2" memory_limit = "5Gi" # service containers service_cpu_limit = "1" service_memory_limit = "1Gi" # helper container helper_cpu_limit = "1" helper_memory_limit = "1Gi" [runners.kubernetes.volumes] [[runners.kubernetes.volumes.host_path]] name = "var-dbus" host_path = "/var/run/dbus" mount_path = "/var/run/dbus" read_only = false [[runners.kubernetes.volumes.host_path]] name = "run-dbus" host_path = "/run/dbus" mount_path = "/run/dbus" read_only = false ## Configure environment variables that will be present when the registration command runs ## This provides further control over the registration process and the config.toml file ## ref: ## ref: https://docs.gitlab.com/runner/configuration/advanced-configuration.html ## envVars: - name: HOME value: /home/gitlab-runner