数以千计的gitlab使用者不断增加我该如何阻止呢？

如何解决数以千计的gitlab使用者不断增加我该如何阻止呢？

我正在运行Gitlab-ce 13.5.3（目前有最新版本）。 Gitlab的Nginx反向代理后面带有官方的docker镜像。 另外，我使用的是官方gitlab-runner码头工人镜像。

我注册了gitlab运行程序，但这是问题所在：gitlab运行程序的数量正在增长。当我计数超过8.500个gitlab-runners时，我停止了它。 我在做什么错了？

所以这是我的docker-compose（有点简化，我省略了本地端口或电子邮件配置）：

version: '2'
services:
  web:
    image: 'gitlab/gitlab-ce:latest'
    restart: unless-stopped
    hostname: 'gitlab.myserver.com'
    environment:
      GITLAB_OMNIBUS_CONFIG: |
        external_url 'https://gitlab.myserver.com'
        letsencrypt['enable'] = false
        nginx['listen_port'] = 80
        nginx['listen_https'] = false
    networks:
      - gitlab

  gitlab-runner:
    image: gitlab/gitlab-runner:alpine
    restart: unless-stopped
    depends_on:
      - web
    volumes:
      - ./config/gitlab-runner:/etc/gitlab-runner
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - gitlab

networks:
  gitlab:

这是我注册gitlab-runner的方式。我只运行了此命令一次！

docker-compose run --entrypoint "gitlab-runner register \
  --non-interactive \
  --url https://gitlab.myserver.com/ \
  --registration-token XXXXXXXXXXXXXXXX \
  --executor docker \
  --docker-image alpine:latest \
  --description docker-runner \
  --tag-list docker \
  --run-untagged=true \
  --locked=false \
 " gitlab-runner

这是docker ps

CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS                          PORTS                                                                NAMES
06efXXXXXXX        gitlab/gitlab-runner:alpine   "gitlab-runner regis…"   3 minutes ago       Restarting (0) 12 seconds ago                                                                        gitlab_gitlab-runner_run_2
085fXXXXXXX        gitlab/gitlab-runner:alpine   "/usr/bin/dumb-init …"   14 hours ago        Up 3 minutes                                                                                         gitlab_gitlab-runner_1
538XXXXXXXX        gitlab/gitlab-ce:latest       "/assets/wrapper"        14 hours ago        Up 14 hours (healthy)           0.0.0.0:XXX->22/tcp,0.0.0.0:XXX->80/tcp,0.0.0.0:XXX->443/tcp   gitlab_web_1

这是docker logs gitlab_gitlab-runner_run_2

Registering runner... succeeded                     runner=vrTo69h7
Runner registered successfully. Feel free to start it,but if it's running already the config should be automatically reloaded! 
Runtime platform                                    arch=amd64 os=linux pid=1 revision=ece86343 version=13.5.0
Running in system-mode.                            
                                                   
Registering runner... succeeded                     runner=vrTo69h7
Runner registered successfully. Feel free to start it,but if it's running already the config should be automatically reloaded! 
Runtime platform                                    arch=amd64 os=linux pid=1 revision=ece86343 version=13.5.0
Running in system-mode.                            

如您所见，它一直重复Registering runner... succeeded runner=vrTo69h7。但为什么？我该怎么阻止？

这是我的config/gitlab-runner/config.toml（我只写了前4行，所有runners都是自动添加的）

concurrent = 1
check_interval = 0

[session_server]
  session_timeout = 1800

[[runners]]
  name = "docker-runner"
  url = "https://gitlab.myserver.com/"
  token = "MsmyqXXXXXXXXXXXX"
  executor = "docker"
  [runners.custom_build_dir]
  [runners.cache]
    [runners.cache.s3]
    [runners.cache.gcs]
    [runners.cache.azure]
  [runners.docker]
    tls_verify = false
    image = "alpine:latest"
    privileged = false
    disable_entrypoint_overwrite = false
    oom_kill_disable = false
    disable_cache = false
    volumes = ["/cache"]
    shm_size = 0

[[runners]]
  name = "docker-runner"
  url = "https://gitlab.myserver.com/"
  token = "hToUnJXXXXXXXXXXXX"
  executor = "docker"
  [runners.custom_build_dir]
  [runners.cache]
    [runners.cache.s3]
    [runners.cache.gcs]
    [runners.cache.azure]
  [runners.docker]
    tls_verify = false
    image = "alpine:latest"
    privileged = false
    disable_entrypoint_overwrite = false
    oom_kill_disable = false
    disable_cache = false
    volumes = ["/cache"]
    shm_size = 0

[[runners]]
  .... and many many more like that ....!

这是gitlab中的错误还是我弄乱了配置？

谢谢！

PS：也许我是在写那个的时候找到了原因。我检查了docker logs gitlab_gitlab-runner_1并发现

WARNING: Checking for jobs... failed                runner=ZaP14Mxb status=502 Proxy Error
WARNING: Checking for jobs... failed                runner=siym2jms status=502 Bad Gateway

这也许是因为用docker-compose重新启动后，我的反向代理最多需要30秒才能检测到gitlab再次运行。

当我停止docker服务gitlab-runner并再次启动它时，这些错误消息消失了，转轮的人数目前没有增加。

但我不了解的是，不仅在最初的30秒内，每分钟都有几位新的跑步者出现。所以这仍然让我感到困惑。