gitlab-runner执行作业时如何避免与当前容器端口冲突

How to avoid port conflict with current container while gitlab-runner execute the job

我正在尝试使用 gitlab-runner 部署我的应用程序。

这是.gitlab-ci.yml脚本:

stages:
  - build
  - deploy

image: docker:20

variables:
  IMAGE_NAME: front:$CI_COMMIT_REF_NAME

build:
  stage: build
  when: manual
  script:
    - docker build -t $IMAGE_NAME .
    - docker run -dp 80:80 $IMAGE_NAME
  only:
    - master
    - tags
  tags:
    - front

第一次执行后一切正常,我的应用程序有一个 运行 容器。但是在执行下一个作业时出现错误:

$ docker run -dp 80:80 $IMAGE_NAME
956d5a27449df0d38db357256fb96cf8cab8ba689d05fda21e54552bbe93fb7a
docker: Error response from daemon: driver failed programming external connectivity on endpoint frosty_elion (d89b1f150968331727a7c00823c28f3ab6a80f7882d659fce3520834005ad197): Bind for 0.0.0.0:80 failed: port is already allocated.
Cleaning up file based variables
ERROR: Job failed: exit code 125

问题:如何避免与仍在使用所需端口的 运行 容器发生冲突?

这是 gitlab-runner config.toml:

concurrent = 1
check_interval = 0

[session_server]
  session_timeout = 1800

[[runners]]
  name = "name"
  url = "url"
  token = "token"
  executor = "docker"
  [runners.custom_build_dir]
  [runners.cache]
    [runners.cache.s3]
    [runners.cache.gcs]
    [runners.cache.azure]
  [runners.docker]
    tls_verify = false
    image = "docker:latest"
    privileged = true
    disable_entrypoint_overwrite = false
    oom_kill_disable = false
    disable_cache = false
    volumes = ["/var/run/docker.sock:/var/run/docker.sock", "/cache"]
    shm_size = 0

构建脚本不会自动清除您使用的容器 运行。您需要确保容器已停止,如下所示:

build:
  stage: build
  when: manual
  script:
    - docker build -t $IMAGE_NAME .
    - (docker stop test_deployment_80 || true)
    - docker run -dp --rm --name test_deployment_80 80:80 $IMAGE_NAME
  only:
    - master
    - tags
  tags:
    - front

在这里,我将 --rm 添加到容器中,以便告诉 docker 在容器停止时将其移除。此外,我添加了 --name 以获得 运行 容器的可识别名称。在启动新容器之前,我使用上一个命令中的名称来停止容器。