Quickstart: Deploy your first container app with containerapp up

The Azure Container Apps service enables you to run microservices and containerized applications on a serverless platform. With Container Apps, you enjoy the benefits of running containers while you leave behind the concerns of manually configuring cloud infrastructure and complex container orchestrators.

In this quickstart, you create and deploy your first container app using the az containerapp up command.

Prerequisites

• An Azure account with an active subscription.
  • If you don't have one, you can create one for free.
• Install the Azure CLI.

Setup

To sign in to Azure from the CLI, run the following command and follow the prompts to complete the authentication process.

Bash

az login

Azure PowerShell

az login

Ensure you're running the latest version of the CLI via the upgrade command.

Bash

az upgrade

Azure PowerShell

az upgrade

Next, install or update the Azure Container Apps extension for the CLI.

Bash

az extension add --name containerapp --upgrade

Azure PowerShell

az extension add --name containerapp --upgrade

Register the Microsoft.App and Microsoft.OperationalInsights namespaces if you haven't already registered them in your Azure subscription.

Bash

az provider register --namespace Microsoft.App

az provider register --namespace Microsoft.OperationalInsights

Azure PowerShell

az provider register --namespace Microsoft.App

az provider register --namespace Microsoft.OperationalInsights

Now that your Azure CLI setup is complete, you can define the environment variables that are used throughout this article.

Create a resource group

az group create --location centralus --resource-group my-container-apps

Create and deploy the container app

Create and deploy your first container app with the containerapp up command. This command will:

• Create the Container Apps environment
• Create the Log Analytics workspace
• Create and deploy the container app using a public container image

Note that if any of these resources already exist, the command will use them instead of creating new ones.

Bash

az containerapp up \
  --name my-container-app \
  --resource-group my-container-apps \
  --location centralus \
  --environment 'my-container-apps' \
  --image mcr.microsoft.com/k8se/quickstart:latest \
  --target-port 80 \
  --ingress external \
  --query properties.configuration.ingress.fqdn

Azure PowerShell

az containerapp up `
  --name my-container-app `
  --resource-group my-container-apps `
  --location centralus `
  --environment  my-container-apps `
  --image mcr.microsoft.com/k8se/quickstart:latest `
  --target-port 80 `
  --ingress external `
  --query properties.configuration.ingress.fqdn

Note

Make sure the value for the --image parameter is in lower case.

By setting --ingress to external, you make the container app available to public requests.

Verify deployment

The up command returns the fully qualified domain name for the container app. Copy this location to a web browser.

The following message is displayed when the container app is deployed:

Clean up resources

If you're not going to continue to use this application, run the following command to delete the resource group along with all the resources created in this quickstart.

Caution

The following command deletes the specified resource group and all resources contained within it. If resources outside the scope of this quickstart exist in the specified resource group, they will also be deleted.

az group delete --name my-container-apps

Tip

Having issues? Let us know on GitHub by opening an issue in the Azure Container Apps repo.

Next steps

Communication between microservices