You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-registry/container-registry-get-started-portal.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
title: Quickstart - Create registry in portal
3
3
description: Quickly learn to create a private Docker registry in Azure Container Registry with the Azure portal.
4
4
ms.topic: quickstart
5
-
ms.date: 01/22/2019
5
+
ms.date: 02/13/2020
6
6
ms.custom: "seodec18, mvc"
7
7
---
8
8
# Quickstart: Create a private container registry using the Azure portal
9
9
10
-
An Azure container registry is a private Docker registry in Azure where you can store and manage your private Docker container images. In this quickstart, you create a container registry with the Azure portal. Then, use Docker commands to push a container image into the registry, and finally pull and run the image from your registry.
10
+
An Azure container registry is a private Docker registry in Azure where you can store and manage private Docker container images and related artifacts. In this quickstart, you create a container registry with the Azure portal. Then, use Docker commands to push a container image into the registry, and finally pull and run the image from your registry.
11
11
12
12
To log in to the registry to work with container images, this quickstart requires that you are running the Azure CLI (version 2.0.55 or later recommended). Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][azure-cli].
![Creating a container registry in the Azure portal][qs-portal-01]
25
25
26
-
Enter values for **Registry name** and **Resource group**. The registry name must be unique within Azure, and contain 5-50 alphanumeric characters. For this quickstart create a new resource group in the `West US` location named `myResourceGroup`, and for **SKU**, select 'Basic'. Select **Create** to deploy the ACR instance.
26
+
On the **Basics** screen, enter values for **Registry name** and **Resource group**. The registry name must be unique within Azure, and contain 5-50 alphanumeric characters. For this quickstart create a new resource group in the `West US` location named `myResourceGroup`, and for **SKU**, select 'Basic'.
27
27
28
28
![Create container registry in the Azure portal][qs-portal-03]
29
29
30
+
Accept default values for the remaining settings. Then select **Review + create**. After reviewing the settings, select **Create**.
31
+
32
+
30
33
In this quickstart you create a *Basic* registry, which is a cost-optimized option for developers learning about Azure Container Registry. For details on available service tiers, see [Container registry SKUs][container-registry-skus].
31
34
32
35
When the **Deployment succeeded** message appears, select the container registry in the portal.
@@ -37,7 +40,7 @@ Take note of the value of the **Login server**. You use this value in the follow
37
40
38
41
## Log in to registry
39
42
40
-
Before pushing and pulling container images, you must log in to the ACR instance. Open a command shell in your operating system, and use the [az acr login][az-acr-login] command in the Azure CLI.(Specify only Container Name. Do not include 'azurecr.io')
43
+
Before pushing and pulling container images, you must log in to the ACR instance. Open a command shell in your operating system, and use the [az acr login][az-acr-login] command in the Azure CLI.(Specify only the registry name. Don't include the 'azurecr.io' suffix.)
0 commit comments