Gitlab Runner挂载PVC为缓存目录失败及缓存适配器错误排查

核心问题分析 #

• 任务Pod未挂载PVC：当前配置仅给Runner主容器挂载了PVC，但未正确配置让Runner创建的任务Pod挂载该PVC
• 缓存适配器错误：cache factory not found是因为缓存配置存在冲突，同时定义了全局缓存和Kubernetes executor专属缓存，导致Runner无法识别正确的缓存适配器

修正后的Helm配置 #

runners:
  privileged: true
  config: |
    [[runners]]
      cache_dir = "/cache"
      [runners.cache]
        type = "file"
        [runners.cache.file]
          path = "/cache"
      [runners.kubernetes]
        disable_cache = false
        helper_image = "gitlab/gitlab-runner-helper:alpine3.13-arm64-bleeding"
        image = "arm64v8/ubuntu:22.04"
        namespace = "{{.Release.Namespace}}"
        privileged = true
        pull_policy = ["always"]
        # 配置任务Pod挂载PVC，同时覆盖helper容器的挂载路径
        [runners.kubernetes.volumes.pvc]
          name = "gitlab-pvc"
          mount_path = "/cache"
          mount_path_helper = "/cache"

关键配置说明 #

• 移除主容器的volumeMounts和volumes：这两项是给Runner控制容器用的，我们需要的是任务Pod挂载PVC，因此无需保留
• 完善PVC挂载配置：添加mount_path_helper = "/cache"，确保负责缓存操作的GitLab Runner Helper容器也挂载该PVC
• 简化缓存配置：只保留[runners.cache]的file类型配置，删除冗余的[runners.kubernetes.cache]配置，避免冲突。Kubernetes executor下，只要任务Pod挂载了PVC，file类型缓存即可正常工作

验证步骤 #

1. 应用修正后的Helm配置：helm upgrade gitlab-runner gitlab/gitlab-runner -f your-values.yaml
2. 触发CI任务后，查看任务Pod详情：kubectl describe pod <job-pod-name>，确认gitlab-pvc已挂载到/cache路径
3. 检查CI任务日志，确认缓存相关错误消失

内容的提问来源于stack exchange，提问作者T00rk