You need to enable JavaScript to run this app. AWS EB Docker-Compose拉取GitLab私有镜像二次部署报访问被拒
优惠活动
大模型
产品
解决方案
定价
更多

AWS EB Docker-Compose拉取GitLab私有镜像二次部署报访问被拒

AWS Elastic Beanstalk Docker Compose 部署时重部署拉取GitLab私有镜像报权限错误

问题概述

我正在实现基于docker-compose的应用部署到AWS Elastic Beanstalk的流程,流程中需要从GitLab托管的私有镜像仓库拉取Docker镜像。

  • 首次部署完全正常:系统从私有镜像仓库拉取镜像,使用docker-compose启动容器,由Django提供服务的网页可通过主机正常访问。
  • 但使用完全相同的docker-compose配置、同一Docker镜像执行新版本部署时,拉取镜像环节就会报错,错误日志如下:
2021/03/16 09:28:34.957094 [ERROR] An error occurred during execution of command [app-deploy] - [Run Docker Container]. Stop running the command. Error: failed to run docker containers: Command /bin/sh -c docker-compose up -d failed with error exit status 1. Stderr:Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
Creating network "current_default" with the default driver
Pulling redis (redis:alpine)...
Pulling mysql (mysql:5.7)...
Pulling project.dockertest(registry.gitlab.com/company/spikes/dockertest:latest)...
Get https://registry.gitlab.com/v2/company/spikes/dockertest/manifests/latest: denied: access forbidden

2021/03/16 09:28:34.957104 [INFO] Executing cleanup logic

环境配置

  • 运行环境:AWS Elastic Beanstalk 64位 Amazon Linux 2/3.2
  • GitLab镜像仓库凭证存储在S3桶中,文件名为.dockercfg,内容如下:
{
        "auths": {
                "registry.gitlab.com": {
                        "auth": "base64 encoded username:personal_access_token"
                }
        },
        "HttpHeaders": {
                "User-Agent": "Docker-Client/18.03.1-ce (linux)"
        }
}
  • 项目仓库包含v3版本的Dockerrun.aws.json文件,用于引用S3中的凭证文件,内容如下:
{
  "AWSEBDockerrunVersion": "3",
  "Authentication": {
    "bucket": "gitlab-dockercfg",
    "key": ".dockercfg"
  }
}

复现步骤

  1. 编写使用私有Docker镜像的docker-compose.yml配置文件,配置中对应的镜像可通过S3中dockercfg存储的凭证正常拉取
  2. 创建使用Docker平台的新应用,执行命令:eb init testapplication --platform=docker --region=eu-west-1

注意:所选区域必须与存储dockercfg的S3桶所在区域一致。

  1. 执行首次部署(该操作可成功完成),执行命令:
    eb create testapplication-test --branch_default --cname testapplication-test --elb-type=application --instance-types=t2.micro --min-instance=1 --max-instances=4
    首次部署的日志显示镜像可正常获取并启动,日志片段:
2021/03/16 08:58:07.533988 [INFO] save docker tag command: docker tag 5812dfe24a4f redis:alpine
2021/03/16 08:58:07.533993 [INFO] save docker tag command: docker tag f8fcde8b9ae2 mysql:5.7
2021/03/16 08:58:07.533998 [INFO] save docker tag command: docker tag 1dd9b65d6a9f registry.gitlab.com/company/spikes/dockertest:latest
2021/03/16 08:58:07.534010 [INFO] Running command /bin/sh -c docker rm `docker ps -aq`
  1. 在不修改本地仓库内容、也不改动私有镜像仓库中远端Docker镜像的前提下,执行重部署操作,触发上述报错,执行命令:eb deploy testapplication-test
    本次部署会执行失败,输出片段:
...
2021-03-16 10:02:28    INFO    Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2021-03-16 10:02:29    ERROR   Unsuccessful command execution on instance id(s) 'i-0dc445d118ac14b80'. Aborting the operation.
2021-03-16 10:02:29    ERROR   Failed to deploy application.

实例日志(路径/var/log/eb-engine.log)显示核心报错:

Pulling redis (redis:alpine)...
Pulling mysql (mysql:5.7)...
Pulling project.dockertest (registry.gitlab.com/company/spikes/dockertest:latest)...
Get https://registry.gitlab.com/v2/company/spikes/dockertest/manifests/latest: denied: access forbidden

2021/03/16 10:02:25.902479 [INFO] Executing cleanup logic

已尝试的调试方案

  • 调整S3中的dockercfg文件名(参考网络公开的通用解决方案)
  • 测试使用Docker 1.7+版本之前的旧版Docker配置格式,经验证Amazon Linux 2实例搭配Dockerrun v3可兼容新版格式
  • 验证dockercfg格式正确性:若S3中的dockercfg格式错误,部署时会直接报对应格式错误,可证明EB实例确实会读取使用S3中的dockercfg文件

参考内容

  • AWS Elastic Beanstalk 单容器Docker配置官方说明文档

内容的提问来源于stack exchange,提问作者Tim Muller

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.10.30 01:45:06