我正在尝试使用packer为docker:dind镜像提供配置，该镜像将使用以下构建脚本构建另一个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:dind镜像中配置的默认入口点["dockerd-entrypoint.sh"]，并用自己的入口点 ["/bin/sh"]替换。这会阻止内部运行的docker进程启动，shell脚本也无法执行。
我尝试更改入口点(entrypoint)和run_command选项，但第一种情况下没有产生任何效果(我假设它将在提交镜像时更新)，而在后一种情况下则无法执行任何脚本。
"changes": [
"ENTRYPOINT [dockerd-entrypoint.sh]"
],
"run_command": ["-d", "-i", "-t", "--entrypoint=dockerd-entrypoint.sh", "--", "{{.Image}}"]
另一个选项是将“[dockerd-entrypoint.sh]”作为内联Shell脚本运行（第一步），但这会阻塞该进程并且不会执行下一步操作。 我已经没有别的选择了，需要帮助理解它是如何工作的，以及是否有解决方案。