Azure部署中心+GitHub Actions访问GHCR被拒问题求助
解决Azure部署中心结合GitHub Actions部署容器应用时GHCR访问被拒的问题
错误原因分析
Error response from daemon: Get "https://ghcr.io/v2/": denied: denied 本质是GHCR(GitHub容器注册表)登录失败或权限不足,结合你的Workflow配置,主要存在以下配置错误:
具体修复步骤
1. 替换GHCR登录凭证
你当前使用的AzureAppService_ContainerUsername_XXX和AzureAppService_ContainerPassword_XXX是Azure容器应用的专属凭证,无法用于登录GHCR。需要改用GitHub的有效凭证:
- 创建GitHub个人访问令牌(PAT),勾选
write:packages、read:packages权限 - 在GitHub仓库的Secrets中新增两个变量:
GHCR_USERNAME(你的GitHub用户名)、GHCR_TOKEN(刚创建的PAT) - 修改登录步骤配置:
- name: Log in to registry uses: docker/login-action@v2 with: registry: ghcr.io username: ${{ secrets.GHCR_USERNAME }} password: ${{ secrets.GHCR_TOKEN }}
2. 修正镜像标签格式
GHCR的镜像标签规则为ghcr.io/<GitHub用户名>/<镜像名称>:<版本标签>,你当前的标签包含mcr.microsoft.com/appsvc/staticsite,属于无效路径,会导致镜像推送失败。修改为:
tags: ghcr.io/${{ secrets.GHCR_USERNAME }}/aeris-qai:${{ github.sha }}
(aeris-qai可替换为你自定义的镜像名称,只要符合GHCR命名规范即可)
3. 保持部署步骤的镜像地址一致
部署步骤中的images参数必须和构建推送的镜像标签完全匹配,同步修改为:
images: 'ghcr.io/${{ secrets.GHCR_USERNAME }}/aeris-qai:${{ github.sha }}'
4. 关于源码vs镜像的疑问
你的思路是正确的:Azure部署中心结合GitHub Actions支持通过源码+Dockerfile自动构建镜像并完成部署,不需要提前准备好成品镜像文件。只要Dockerfile配置合法,Workflow可以完成从代码拉取、镜像构建、镜像推送再到Azure部署的全流程。
修复后的完整Workflow示例
# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy # More GitHub Actions for Azure: https://github.com/Azure/actions name: Build and deploy container app to Azure Web App - aeris-qai on: push: branches: - main workflow_dispatch: jobs: build: runs-on: 'ubuntu-latest' steps: - uses: actions/checkout@v2 - name: Set up Docker Buildx uses: docker/setup-buildx-action@v2 - name: Log in to GHCR uses: docker/login-action@v2 with: registry: ghcr.io username: ${{ secrets.GHCR_USERNAME }} password: ${{ secrets.GHCR_TOKEN }} - name: Build and push container image to GHCR uses: docker/build-push-action@v3 with: push: true tags: ghcr.io/${{ secrets.GHCR_USERNAME }}/aeris-qai:${{ github.sha }} file: ./Dockerfile deploy: runs-on: ubuntu-latest needs: build environment: name: 'production' url: ${{ steps.deploy-to-webapp.outputs.webapp-url }} steps: - name: Deploy to Azure Web App id: deploy-to-webapp uses: azure/webapps-deploy@v2 with: app-name: 'XXXX' slot-name: 'production' publish-profile: ${{ secrets.AzureAppService_PublishProfileXXX }} images: 'ghcr.io/${{ secrets.GHCR_USERNAME }}/aeris-qai:${{ github.sha }}'
内容的提问来源于stack exchange,提问作者Badrul
相关产品推荐
相关产品推荐

