This weblog was co-authored by MacKenzie Olson, Program Supervisor, Azure Container Situations.
Right this moment we’re excited in regards to the first launch of the brand new Docker Desktop integration with Microsoft Azure. Final month Microsoft and Docker introduced this collaboration, and at the moment you may expertise it for your self.
The brand new edge launch of Docker Desktop supplies an integration between Docker and Microsoft Azure that allows you to use native Docker instructions to run your purposes as serverless containers with Azure Container Situations.
You should utilize the Docker CLI to rapidly and simply signal into Azure, create a Container Situations context utilizing an Azure subscription and useful resource group, then run your single-container purposes on Container Situations utilizing
docker run. You can too deploy multi-container purposes to Container Situations which can be outlined in a Docker Compose file utilizing
docker compose up.
Code-to-Cloud with serverless containers
Azure Container Situations is a superb answer for operating a single Docker container or an software comprised of a number of containers outlined with a Docker Compose file. With Container Situations, you may run your containers within the cloud without having to arrange any infrastructure and benefit from options similar to mounting Azure Storage and GitHub repositories as volumes. As a result of there isn’t any infrastructure or platform administration overhead, Container Situations caters to those that have to rapidly run containers within the cloud.
Container Situations can be a very good goal to run the identical workloads in manufacturing. In manufacturing circumstances, we advocate leveraging Docker instructions inside an automatic CI/CD circulation. This protects time having to rewrite configuration information as a result of the identical Dockerfile and Docker Compose information may be deployed to manufacturing with instruments similar to GitHub Actions. Container Situations additionally has a pay-as-you-go pricing mannequin, which suggests you’ll solely be billed for CPU and reminiscence consumption per second, solely when the container is operating.
Let’s have a look at the brand new Docker Azure integration utilizing an instance. We’ve got a employee container that frequently pulls orders off a queue and performs essential order processing. Listed here are the steps to run this in Container Situations with native Docker instructions:
Run a single container
As you may see from the above animation, the brand new Docker CLI integration with Azure makes it straightforward to get a container operating in Azure Container Situations. Utilizing solely the Docker CLI you may log in to Azure with multi-factor authentication and create a Docker context utilizing Container Situations because the backend. Detailed data on Container Situations contexts may be discovered within the documentation.
As soon as the brand new Container Situations context is created it may be used to focus on Container Situations with lots of the normal Docker instructions you possible already use; like docker run, docker ps, and docker rm. Working a easy
docker run <picture> command will begin a container in Container Situations utilizing the picture that’s saved in a registry like Docker Hub or Azure Container Registry. You may run different frequent Docker instructions to examine, attach-to, and look at logs from the operating container.
Use Docker Compose to deploy a multi-container app
We see many containerized purposes that consist of some associated containers. Sidecar containers typically carry out logging or signing providers for the primary container. With the brand new Docker Azure integration, you need to use Docker Compose to explain these multi-container purposes.
You should utilize a Container Situations context and a Docker Compose file as a part of your edit-build-debug inside loop, in addition to your CI/CD flows. This allows you to use docker compose up and down instructions to spin up or shut down a number of containers without delay in Container Situations.
Visual Studio Code for a good higher expertise
The Visual Studio Code Docker extension supplies you with an built-in expertise to start out, cease, and handle your containers, photographs, contexts, and extra. Use the extension to scaffold Dockerfiles and Docker Compose information for any language. For Node.js, Python, and .NET, you get built-in, one-click debugging of your app contained in the container. After which in fact there’s the Explorer, which has a number of panels that make the administration of your Docker objects straightforward from proper inside Visual Studio Code.
Use the Containers panel to checklist, begin, cease, examine, view logs, and extra.
From the Photographs panel you may checklist, pull, tag, and push your photographs.
The Contexts panel allows you to checklist all of your contexts and rapidly swap between them. Once you swap context, the opposite panels will refresh to indicate the Docker objects from the chosen context. Container Situations contexts will probably be absolutely supported within the subsequent launch of the docker extension.
Strive it out
To begin utilizing the Docker Azure integration set up the Docker Desktop edge launch. You may leverage the present Visual Studio Code Docker extension at the moment, Container Situations context help will probably be added very quickly.
To study extra in regards to the Docker Desktop launch, you may learn this weblog submit from Docker. Yow will discover extra data within the documentation for utilizing Docker Container Situations contexts.