封隔器码头工人生成器配置码头工人在码头图像

Question

我正在尝试配置docker：使用packer设置图像，这将构建另一个docker镜像并使用以下构建脚本在docker中运行它：

{
  "builders": [
    {
      "type": "docker",
      "image": "docker:dind",
      "privileged": true,
      "commit": "true"
    }
  ],
  "provisioners": [
    {
      "type": "file",
      "source": "../docker/",
      "destination": "/docker"
    },
    {
      "type": "shell",
      "inline": [
        "docker build -t my-service /docker"
      ]
    }
  ],
  "post-processors": [
    [
      {
        "type": "docker-tag",
        "repository": "my-service",
        "tag": "latest"
      }
    ]
  ]
}

当我运行此脚本时，它失败并出现以下错误：

$ packer build build.json
docker output will be in this color.

==> docker: Creating a temporary directory for sharing data...
==> docker: Pulling Docker image: docker:dind
    docker: dind: Pulling from library/docker
    docker: Digest: sha256:21fe82c6e54e2db31e64f79ec7ac75c6a8f7469cdc56687ced97d6fc3e75e6cd
    docker: Status: Image is up to date for docker:dind
==> docker: Starting docker container...
    docker: Run command: docker run --privileged -v C:\Users\user\packer.d\tmp:/packer-files -d -i -t --entrypoint=/bin/sh -- docker:dind
    docker: Container ID: 7fa2ae91eaf6111ce6d0567f1e523100c777311449454b0df8d6d49c84c477d6
==> docker: Using docker communicator to connect: 172.17.0.2
==> docker: Uploading ../docker/ => /docker
==> docker: Provisioning with shell script: C:\Users\user\AppData\Local\Temp\packer-shell164551847
==> docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
==> docker: Killing the container: 7fa2ae91eaf6111ce6d0567f1e523100c777311449454b0df8d6d49c84c477d6
Build 'docker' errored: Script exited with non-zero exit status: 1.Allowed exit codes are: [0]

==> Some builds didn't complete successfully and had errors:
--> docker: Script exited with non-zero exit status: 1.Allowed exit codes are: [0]

==> Builds finished but no artifacts were created.

问题是，当packer启动容器时，它会覆盖在docker中配置的默认入口点[“dockerd-entrypoint.sh”]：dind image带有它自己的入口点[“/ bin / sh”]。这可以防止docker进程内的docker启动，并且无法执行shell脚本。

我尝试使用以下选项更改entrypoint和run_command，但在第一种情况下它没有任何效果（我假设它将在提交映像时最后更新），而后者则无法执行任何脚本。

"changes": [
  "ENTRYPOINT [dockerd-entrypoint.sh]"
],
"run_command": ["-d", "-i", "-t", "--entrypoint=dockerd-entrypoint.sh", "--", "{{.Image}}"]

另一种选择是将“[dockerd-entrypoint.sh]”作为内联shell脚本（第一个）运行，但这会阻止该进程并且不执行后续步骤。

我已经没有选择了，我需要一些帮助来理解它是如何工作的，以及是否有一些解决方案。

Answer 1

在你的inline部分开始在后台运行docker守护进程，例如dockerd-entrypoint.sh & sleep 5。