Skip to content

Fix build-and-deploy by forcing registry-qualified Docker image build path - #2

Draft
mattia1208 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-build-and-deploy
Draft

mattia1208 with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-build-and-deploy

Conversation

Copilot AI commented Jul 8, 2026 •

Copy link
Copy Markdown

The build-and-deploy GitHub Actions job was failing in the Azure Container Apps deploy step due to an invalid build path selection. Log analysis showed the action falling back to source-based Cloud Build/Oryx, which failed during analyzer execution.

  • Root cause

    • registryUrl was empty in the workflow.
    • imageToBuild was not fully registry-qualified, allowing the deploy action to take the source-build fallback path.
  • Changes

    • Workflow input correction (.github/workflows/overleaf-AutoDeployTrigger-d87fc5c7-63af-4c3b-a752-65e5ec8b9a26.yml)
      • Set registryUrl: docker.io
      • Set imageToBuild: docker.io/default/overleaf:${{ github.sha }}
  • Config diff (key lines)

    with:
      appSourcePath: ${{ github.workspace }}
      dockerfilePath: server-ce/Dockerfile
      registryUrl: docker.io
      imageToBuild: docker.io/default/overleaf:${{ github.sha }}

Copilot AI changed the title [WIP] Fix failing GitHub Actions job 'build-and-deploy' Fix build-and-deploy by forcing registry-qualified Docker image build path Jul 8, 2026
Copilot AI requested a review from mattia1208 July 8, 2026 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants