Azure Container Registry is Not deployed with Main Bicep Template

[honestypugh2]

This issue is related to #346 .

Currently Azure Container Registry (ACR) is not deployed with the bicep template at main.bicep.

Requesting support to update the code and Deployment Guide to allow the deployment to allow Azure Container Registry to be the DEFAULT Image Source rather than the current implementation that only has Docker Hub as the Image Source with ACR not deployed.

Below is a screenshot of current deployment services that does not include Azure Container Registry and with Image Source set to Docker Hub:

Currently this step in the Deployment Guide fails since ACR is not deployed or even apart of the bicep templates.

[Sushilkumar-Microsoft]

Thanks @honestypugh2 for reporting, we will look into this and keep you posted.

[Vamshi-Microsoft]

Hey @honestypugh2 The current deployment flow does not use the USE_LOCAL_BUILD flag, and the Azure Container Registry (ACR) resource is not deployed automatically through azd up.

We are in the process of updating the Deployment Guide to reflect the accurate deployment steps.

In the meantime, to build and push the latest container image to your Azure Container Registry, follow these steps:

Create a new Azure Container Registry

If you don’t already have one, create a new ACR using the Azure Portal or CLI.

Run the following commands from your terminal

Backend

az acr login --name <containerregname>
docker build -f src/backend/Dockerfile -t <acrloginserver>/<repo>:<tagname> .
docker push <acrloginserver>/<repo>:<tagname>

Frontend

az acr login --name <containerregname>
docker build -f src/frontend/Dockerfile -t <acrloginserver>/<repo>:<tagname> .
docker push <acrloginserver>/<repo>:<tagname>

We are working on implementing container publishing to ACR as part of a post-deployment script. We'll keep you updated on progress.

[honestypugh2]

Thank you for the update!