|
1 | 1 | --- |
2 | | -title: 'Quickstart: Deploy an Existing Container Image in the Azure Portal' |
3 | | -description: Deploy an existing container image to Azure Container Apps by using the Azure portal. |
| 2 | +title: 'Quickstart: Deploy an existing container image in the Azure portal' |
| 3 | +description: Deploy an existing container image to Azure Container Apps using the Azure portal. |
4 | 4 | services: container-apps |
5 | 5 | author: craigshoemaker |
6 | 6 | ms.service: azure-container-apps |
7 | 7 | ms.topic: quickstart |
8 | | -ms.date: 03/24/2026 |
| 8 | +ms.date: 10/14/2024 |
9 | 9 | ms.author: cshoe |
| 10 | +zone_pivot_groups: container-apps-registry-types |
10 | 11 | --- |
11 | 12 |
|
12 | 13 | # Quickstart: Deploy an existing container image in the Azure portal |
13 | 14 |
|
14 | | -Azure Container Apps allows you to run microservices and containerized applications on a serverless platform. With Container Apps, you enjoy the benefits of running containers while leaving behind the concerns of manually configuring cloud infrastructure and complex container orchestrators. |
| 15 | +Azure Container Apps enables you to run microservices and containerized applications on a serverless platform. With Container Apps, you enjoy the benefits of running containers while leaving behind the concerns of manually configuring cloud infrastructure and complex container orchestrators. |
15 | 16 |
|
16 | | -This article demonstrates how to deploy an existing container to Azure Container Apps by using the Azure portal. |
| 17 | +This article demonstrates how to deploy an existing container to Azure Container Apps using the Azure portal. |
17 | 18 |
|
18 | 19 | > [!NOTE] |
19 | 20 | > Private registry authorization is supported via registry username and password. |
20 | 21 |
|
21 | 22 | ## Prerequisites |
22 | 23 |
|
23 | | -- An Azure account with an active subscription. If you don't have one, you can [create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn). |
| 24 | +- Azure account with an active subscription. |
| 25 | + - If you don't have one, you [can create one for free](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn). |
| 26 | +## Setup |
| 27 | + |
| 28 | +Begin by signing in to the [Azure portal](https://portal.azure.com). |
24 | 29 |
|
25 | 30 | ## Create a container app |
26 | 31 |
|
27 | 32 | To create your container app, start at the Azure portal home page. |
28 | 33 |
|
29 | | -1. Sign in to the [Azure portal](https://portal.azure.com). |
30 | | - |
31 | | -1. Search for and select **Container Apps** in the search bar. |
32 | | - |
33 | | -1. Select the **Create** button, then choose **+ Container App**. |
| 34 | +1. Search for **Container Apps** in the top search bar. |
| 35 | +1. Select **Container Apps** in the search results. |
| 36 | +1. Select the **Create** button. |
34 | 37 |
|
35 | 38 | ### Basics tab |
36 | 39 |
|
37 | | -On the **Basics** tab, enter the following information: |
| 40 | +In the *Basics* tab, do the following actions. |
| 41 | + |
| 42 | +#### Enter project details |
38 | 43 |
|
39 | 44 | | Setting | Action | |
40 | 45 | |---|---| |
41 | 46 | | Subscription | Select your Azure subscription. | |
42 | | -| Resource group | Select **Create new** and enter *my-container-apps*. | |
43 | | -| Container app name | Enter *my-container-app*. | |
44 | | -| Optimize for Azure Functions | Leave the checkbox unchecked. | |
45 | | -| Deployment source | Select **Container image**. | |
46 | | -| Region | Select **Canada Central**. | |
47 | | -| Container Apps environment | Accept the default. | |
| 47 | +| Resource group | Select **Create new** and enter **my-container-apps**. | |
| 48 | +| Container app name | Enter **my-container-app**. | |
| 49 | + |
| 50 | +#### Create an environment |
48 | 51 |
|
49 | | -Select **Next: Container**. |
| 52 | +1. In the *Create Container App environment* field, select **Create new**. |
| 53 | +1. In the *Create Container App Environment* page on the *Basics* tab, enter the following values: |
50 | 54 |
|
51 | | -### Container tab |
| 55 | + | Setting | Value | |
| 56 | + |---|---| |
| 57 | + | Environment name | Enter **my-environment**. | |
| 58 | + | Region | Select **Canada Central**. | |
52 | 59 |
|
53 | | -On the **Container** tab, enter the following information: |
| 60 | +1. Select the **Monitoring** tab to create a Log Analytics workspace. |
| 61 | +1. Select **Create new** in the *Log Analytics workspace* field. |
| 62 | +1. Enter **my-container-apps-logs** in the *Name* field of the *Create new Log Analytics Workspace* dialog. |
| 63 | + |
| 64 | + The *Location* field is pre-filled with *Canada Central* for you. |
54 | 65 |
|
| 66 | +1. Select **OK**. |
| 67 | +1. Select the **Create** button at the bottom of the *Create Container App Environment* page. |
| 68 | +1. Select the **Next: App settings** button at the bottom of the page. |
| 69 | + |
| 70 | +### App settings tab |
| 71 | + |
| 72 | +In the *App settings* tab, do the following actions: |
| 73 | + |
| 74 | +::: zone pivot="container-apps-private-registry" |
55 | 75 | | Setting | Action | |
56 | 76 | |---|---| |
57 | | -| Use quickstart image | Uncheck the checkbox. | |
58 | | -| Name | Enter *my-portal-app*. | |
| 77 | +| Use quickstart image | **Uncheck** the checkbox. | |
| 78 | +| Name | Enter **my-portal-app**. | |
59 | 79 | | Image source | Select your container image repository source. If your container is hosted in a registry other than **Azure Container Registry**, select **Docker Hub or other registries**. | |
60 | | -| Subscription | Select your Azure subscription. | |
61 | | -| Registry | Select your registry. | |
62 | | -| Image and image tag | Enter the image name, including tag. | |
63 | | - |
64 | | -Select **Next: Ingress**. |
| 80 | +| Image type | Select **Private**. | |
| 81 | +| Registry login server | Enter the domain (including subdomain) of your container registry. | |
| 82 | +| Registry user name | Enter your user name for the registry. | |
| 83 | +| Registry password | Enter your password for the registry. | |
| 84 | +| Image and tag | Enter the image name, including tag. | |
| 85 | +::: zone-end |
| 86 | + |
| 87 | +::: zone pivot="container-apps-public-registry" |
| 88 | +| Setting | Action | |
| 89 | +|---|---| |
| 90 | +| Use quickstart image | **Uncheck** the checkbox. | |
| 91 | +| Name | Enter **my-portal-app**. | |
| 92 | +| Image source | Select your container image repository source. If your container is hosted in a registry other than **Azure Container Registry**, select **Docker Hub or other registries**. | |
| 93 | +| Registry login server | Enter the domain (including subdomain) of your container registry. | |
| 94 | +| Image type | Select **Public**. | |
| 95 | +| Image and tag | Enter the image name, including tag. | |
| 96 | +::: zone-end |
65 | 97 |
|
66 | | -### Ingress tab |
| 98 | +#### Application ingress settings |
67 | 99 |
|
68 | 100 | | Setting | Action | |
69 | 101 | |---|---| |
70 | | -| Ingress | Check or uncheck the checkbox. | |
| 102 | +| Ingress | Select **Enabled** or **Disabled**. | |
71 | 103 |
|
72 | | -If you checked the box to enable ingress, configure the following settings: |
| 104 | +If you enabled ingress, configure the following settings: |
73 | 105 |
|
74 | 106 | | Setting | Action | |
75 | 107 | |---|---| |
76 | | -| Ingress traffic | Select **Limited to Container App Environment** to restrict traffic to this container app. Select **Accepting traffic from anywhere** to publicly expose your container app. | |
| 108 | +| Ingress visibility | Select **Internal** to only allow ingress from other apps in the same virtual network, and select **External** to publicly expose your container app. | |
77 | 109 | | Target port | Enter the port you want to expose your container app. | |
78 | 110 |
|
79 | 111 | ### Deploy the container app |
80 | 112 |
|
81 | | -1. Select the **Review and create** button. |
| 113 | +1. Select the **Review and create** button at the bottom of the page. |
82 | 114 |
|
83 | | - If no errors are found, the **Create** button is enabled. |
| 115 | + Next, the settings in the Container App are verified. If no errors are found, the *Create* button is enabled. |
84 | 116 |
|
85 | | - If there are errors, any tab containing errors is marked with a red dot. Navigate to the appropriate tab. Fields containing an error are highlighted in red. Once all errors are fixed, select **Review and create** again. |
| 117 | + If there are errors, any tab containing errors is marked with a red dot. Navigate to the appropriate tab. Fields containing an error is highlighted in red. Once all errors are fixed, select **Review and create** again. |
86 | 118 |
|
87 | 119 | 1. Select **Create**. |
88 | 120 |
|
89 | | - A page with the message **Deployment is in progress** is displayed. Once the deployment is successfully completed, you see the message: **Your deployment is complete**. |
| 121 | + A page with the message *Deployment is in progress* is displayed. Once the deployment is successfully completed, you see the message: *Your deployment is complete*. |
90 | 122 |
|
91 | 123 | ### Verify deployment |
92 | 124 |
|
93 | | -You can verify your deployment is successful by querying the Log Analytics workspace. You might need to wait 5 to 10 minutes for the analytics to arrive for the first time before you're able to query the logs. |
94 | | - |
95 | | -1. Select **Go to resource** to view your new container app. |
| 125 | +You can verify your deployment is successful by querying the Log Analytics workspace. You might need to wait a 5 to 10 minutes for the analytics to arrive for the first time before you're able to query the logs. |
96 | 126 |
|
97 | | -1. Under **Monitoring**, select **Logs**. |
| 127 | +After 5 to 10 minutes of creating the container app, follow these steps to view logged messages: |
98 | 128 |
|
99 | | -1. Select **KQL mode** from the menu bar. |
100 | | - |
101 | | -1. Enter the following query: |
| 129 | +1. Select **Go to resource** to view your new container app. |
| 130 | +1. Select **Logs** under the *Monitoring* header. |
| 131 | +1. Select the **Load to editor** button from any of the cards. |
| 132 | +1. Replace the generated code with the following query: |
102 | 133 |
|
103 | 134 | ```text |
104 | 135 | ContainerAppConsoleLogs_CL | where ContainerAppName_s == 'my-container-app' | project ContainerAppName_s, Log_s, TimeGenerated |
105 | 136 | ``` |
106 | 137 |
|
107 | 138 | 1. Select the **Run** button. |
108 | | -
|
109 | 139 | 1. Inspect the results in the table. |
110 | 140 |
|
111 | 141 | ## Clean up resources |
112 | 142 |
|
113 | 143 | If you're not going to continue to use this application, you can delete the Azure Container Apps instance and all the associated services by removing the resource group. |
114 | 144 |
|
115 | | -1. Select your resource group from the **Overview** section, then select the **Delete resource group** button. |
116 | | -
|
117 | | -1. Confirm the resource group name, and then select **Delete**. The process to delete the resource group might take a few minutes to complete. |
| 145 | +1. Select the **my-container-apps** resource group from the *Overview* section. |
| 146 | +1. Select the **Delete resource group** button at the top of the resource group *Overview*. |
| 147 | +1. Enter the resource group name **my-container-apps** in the *Are you sure you want to delete "my-container-apps"* confirmation dialog. |
| 148 | +1. Select **Delete**. |
| 149 | + The process to delete the resource group might take a few minutes to complete. |
118 | 150 |
|
119 | 151 | > [!TIP] |
120 | 152 | > Having issues? Let us know on GitHub by opening an issue in the [Azure Container Apps repo](https://github.com/microsoft/azure-container-apps). |
121 | 153 |
|
122 | | -## Next step |
| 154 | +## Next steps |
123 | 155 |
|
124 | 156 | > [!div class="nextstepaction"] |
125 | 157 | > [Communication between microservices](communicate-between-microservices.md) |
0 commit comments