GitLab Runner: Cache adapter could not be initialized: missing S3 configuration

Some day gitlab runner cache just stop work. Version gitlab-runner=12.0.1

No URL provided, cache will not be downloaded from shared cache server. Instead a local version of cache will be extracted.

Sep 3 13:32:29 review gitlab-runner[354]: ERROR: Could not create cache adapter error=cache adapter could not be initialized: missing S3 configuration

Old configuration
[[runners]]
  name = "review"
  url = "https://gitlabserver:443/ci/"
  token = "token"
  executor = "shell"
  output_limit = 12288
  builds_dir = "/data/builds"
  cache_dir = "/data/cache"
  [runners.cache]
    Type = "s3"
    ServerAddress = "s3.amazonaws.com"
    AccessKey = "AccessKey"
    SecretKey = "SecretKey"
    BucketName = "BucketName"
    BucketLocation = "eu-central-1"
    Insecure = false
    Path = "cache"
    Shared = true
With GitLab Runner 11.3.0, the configuration parameters related to S3 were moved to a dedicated [runners.cache.s3] section. The old format of the configuration with S3 configured directly in [runners.cache] was deprecated with GitLab Runner 11.3.0. With GitLab Runner 12.0.0 the old configuration syntax was removed and is no longer supported.

We need just change configuration in /etc/gitlab-runner/config.toml to
[[runners]]
  name = "review"
  url = "https://gitlabserver:443/ci/"
  token = "token"
  executor = "shell"
  output_limit = 12288
  builds_dir = "/data/builds"
  cache_dir = "/data/cache"
  [runners.cache]
    Type = "s3"
    Path = "cache"
    Shared = true
    [runners.cache.s3]
      ServerAddress = "s3.amazonaws.com"
      AccessKey = "AccessKey"
      SecretKey = "SecretKey"
      BucketName = "BucketName"
      BucketLocation = "eu-central-1"
      Insecure = false
Work perfect with gitlab-runner=12.2.0

Comments

Post a Comment

Popular posts from this blog