Skip to content

Latest commit

 

History

History
114 lines (74 loc) · 4.4 KB

container-registry-get-started-bicep.md

File metadata and controls

114 lines (74 loc) · 4.4 KB
title description services author ms.author ms.date ms.topic ms.service ms.custom
Quickstart - Create registry - Bicep
Learn how to create an Azure container registry by using a Bicep file.
azure-resource-manager
mumian
jgao
09/27/2021
quickstart
azure-resource-manager
mode-api

Quickstart: Create a container registry by using a Bicep file

This quickstart shows how to create an Azure Container Registry instance by using a Bicep file.

[!INCLUDE About Azure Resource Manager]

Prerequisites

If you don't have an Azure subscription, create a free account before you begin.

Review the Bicep file

Use Visual studio code or your favorite editor to create a file with the following content and name it main.bicep:

@minLength(5)
@maxLength(50)
@description('Provide a globally unique name of your Azure Container Registry')
param acrName string = 'acr${uniqueString(resourceGroup().id)}'

@description('Provide a location for the registry.')
param location string = resourceGroup().location

@description('Provide a tier of your Azure Container Registry.')
param acrSku string = 'Basic'

resource acrResource 'Microsoft.ContainerRegistry/registries@2021-06-01-preview' = {
  name: acrName
  location: location
  sku: {
    name: acrSku
  }
  properties: {
    adminUserEnabled: false
  }
}

@description('Output the login server property for later use')
output loginServer string = acrResource.properties.loginServer

The following resource is defined in the Bicep file:

More Azure Container Registry template samples can be found in the quickstart template gallery.

Deploy the Bicep file

To deploy the file you've created, open PowerShell or Azure CLI. If you want to use the integrated Visual Studio Code terminal, select the ctrl + ` key combination. Change the current directory to where the Bicep file is located.

CLI

az group create --name myContainerRegRG --location centralus

az deployment group create --resource-group myContainerRegRG --template-file main.bicep --parameters acrName={your-unique-name}

PowerShell

New-AzResourceGroup -Name myContainerRegRG -Location centralus

New-AzResourceGroupDeployment -ResourceGroupName myContainerRegRG -TemplateFile ./main.bicep -acrName "{your-unique-name}"

Note

Replace {your-unique-name}, including the curly braces, with a unique container registry name.

When the deployment finishes, you should see a message indicating the deployment succeeded.

Review deployed resources

Use the Azure portal or a tool such as the Azure CLI to review the properties of the container registry.

  1. In the portal, search for Container Registries, and select the container registry you created.

  2. On the Overview page, note the Login server of the registry. Use this URI when you use Docker to tag and push images to your registry. For information, see Push your first image using the Docker CLI.

    :::image type="content" source="media/container-registry-get-started-bicep/registry-overview.png" alt-text="Registry overview":::

Clean up resources

When you no longer need the resource, delete the resource group, and the registry. To do so, go to the Azure portal, select the resource group that contains the registry, and then select Delete resource group.

:::image type="content" source="media/container-registry-get-started-bicep/delete-resource-group.png" alt-text="Delete resource group":::

Next steps

In this quickstart, you created an Azure Container Registry with a Bicep file. Continue to the Azure Container Registry tutorials for a deeper look at ACR.

[!div class="nextstepaction"] Azure Container Registry tutorials

For a step-by-step tutorial that guides you through the process of creating a Bicep file, see:

[!div class="nextstepaction"] Quickstart: Create Bicep files with Visual Studio Code