I was working with SQL and in Azure DevOps. When the development team created the microservices, the microservices needed the connection with the SQL database. I used the SQL database to connect the microservices. The microservices were created by Java. I used Azure Container Registry to send the Docker image to the Azure environment. I uploaded the image to Azure Container Registry to use in the AKS environment.
We are using Azure Logic Apps ( /products/microsoft-azure-logic-apps-reviews ) in our integration, in addition to Azure Container Registry ( /products/azure-container-registry-reviews ).
The customers need a container system. In the old days, we used to have binary installations with classic delivery. Now, Azure Container Registry is something related to the packaging of the application. It allows us to package applications and run them anywhere using the application image.
Strategic Head | Azure Services and GRC at Braintree
Real User
Top 10
Jul 1, 2024
It's running behind a big financial and legal customer, who runs Service Fabric behind a front door, servicing local banking containers on an ISV solution developed internally.
We use the solution for image processing. We store and manage images. You can utilize the tools to recognize and organize images. For example, you have an image and gather two more images, each with different versions and tagging system. You should filter different variations of these images. Based on the algorithm, you can generate multiple images and then deploy them using Docker for testing or in AKS. We should know how to create and tag the image as part of microservices.
Solution architect / DevOps tech leader / Backend RestAPI / Frontend React.js at a tech vendor with 10,001+ employees
Real User
Dec 28, 2022
The institution I work in intended to go with the Azure App Service with Docker containers, and Azure Container Registry fits the bill. During the standard Azure DevOps pipeline, the institution built the container and then pushed the container directly to Azure Container Registry. Then, in the next stage of the same DevOps pipeline, the institution pulls the Docker image from the Azure App Service, which is already deployed to Azure Container Registry. Overall, the Azure App Service posts the Docker images through its connection with the Azure Container Registry.
The solution is really useful because whenever you want to deploy the containers, you need to have a place to store those container codes so that they can deploy easily. It is always better to store those codes in the solution itself so that you can deploy them through the pipelines. That is where Azure Container Registry comes into the picture. And also, it can duplicate to different zones and locations.
I am a DevOps consultant. I provide the architecture, assessments, and optimization of the services that we use to build a better infrastructure, and other services. We are basically using Azure Container Registry for a project that we have in the healthcare domain. There, we use the container registry and as well as Azure DevOps, apart from the Azure Cloud and the built release pipeline, along with this container registry and the self-hosted server. I would say that this allows us to build, store, and manage the container images and the artifact in the private registry that Azure provides. It's a managed container registry that we don't need to configure or set up within our premises. It's all in the cloud. The login and the portal id where we can store that information, and the containers. We can also see a list of images located in the repository. For example, I can pull any Docker image using the Docker command. I can then store that image within the repository, within this Docker Registry Container. I don't have to go to the Docker Hub or any other hub. This is one of the safest private repositories over the cloud that I have, that I can use. This is one of the most beneficial solutions to be used over the cloud.
New Technologies Adoption Director at a tech services company with 11-50 employees
Real User
Nov 11, 2020
We use it for some specific machine learning models to take advantage of the elasticity of the containers. This is the main use of containers. Around 80% of our implementation is on the public cloud, but in some cases, we use a hybrid model. Our clients are large businesses.
Sr. SDET at a tech services company with 201-500 employees
Real User
Nov 6, 2020
I work for a logistics business, so we have a few applications and we apply them to Azure. We pull the codes, stop at the Docker images, and then we push it to the Container for tracking.
Azure Container Registry allows you to build, store, and manage container images and artifacts in a private registry for all types of container deployments. Use Azure container registries with your existing container development and deployment pipelines. Use Azure Container Registry Tasks to build container images in Azure on-demand, or automate builds triggered by source code updates, updates to a container's base image, or timers.
I was working with SQL and in Azure DevOps. When the development team created the microservices, the microservices needed the connection with the SQL database. I used the SQL database to connect the microservices. The microservices were created by Java. I used Azure Container Registry to send the Docker image to the Azure environment. I uploaded the image to Azure Container Registry to use in the AKS environment.
We are using Azure Logic Apps ( /products/microsoft-azure-logic-apps-reviews ) in our integration, in addition to Azure Container Registry ( /products/azure-container-registry-reviews ).
The customers need a container system. In the old days, we used to have binary installations with classic delivery. Now, Azure Container Registry is something related to the packaging of the application. It allows us to package applications and run them anywhere using the application image.
It's running behind a big financial and legal customer, who runs Service Fabric behind a front door, servicing local banking containers on an ISV solution developed internally.
We use Azure Container Registry to store our container images and the solution that we build for automation.
We use the solution for image processing. We store and manage images. You can utilize the tools to recognize and organize images. For example, you have an image and gather two more images, each with different versions and tagging system. You should filter different variations of these images. Based on the algorithm, you can generate multiple images and then deploy them using Docker for testing or in AKS. We should know how to create and tag the image as part of microservices.
I currently deploy the application to facilitate CI/CD processes. I'm in the process of identifying and setting it up.
We predominantly use Azure Container Registry in our company for the deployment of secure images to ensure consistency.
We use this solution to build, deploy and manage our container registry within a single integrated tool.
Our primary use case for the solution is storing Docker images on Azure Container Registry, and we deploy it on cloud.
The institution I work in intended to go with the Azure App Service with Docker containers, and Azure Container Registry fits the bill. During the standard Azure DevOps pipeline, the institution built the container and then pushed the container directly to Azure Container Registry. Then, in the next stage of the same DevOps pipeline, the institution pulls the Docker image from the Azure App Service, which is already deployed to Azure Container Registry. Overall, the Azure App Service posts the Docker images through its connection with the Azure Container Registry.
It's a container repository. It's like a Docker hub. With it, you can post the image of the container right there.
I'm a cloud infrastructure consultant and we have a partnership with Azure.
The solution is really useful because whenever you want to deploy the containers, you need to have a place to store those container codes so that they can deploy easily. It is always better to store those codes in the solution itself so that you can deploy them through the pipelines. That is where Azure Container Registry comes into the picture. And also, it can duplicate to different zones and locations.
I mainly use Container Registry to containerize applications and ship/deploy them.
I am a DevOps consultant. I provide the architecture, assessments, and optimization of the services that we use to build a better infrastructure, and other services. We are basically using Azure Container Registry for a project that we have in the healthcare domain. There, we use the container registry and as well as Azure DevOps, apart from the Azure Cloud and the built release pipeline, along with this container registry and the self-hosted server. I would say that this allows us to build, store, and manage the container images and the artifact in the private registry that Azure provides. It's a managed container registry that we don't need to configure or set up within our premises. It's all in the cloud. The login and the portal id where we can store that information, and the containers. We can also see a list of images located in the repository. For example, I can pull any Docker image using the Docker command. I can then store that image within the repository, within this Docker Registry Container. I don't have to go to the Docker Hub or any other hub. This is one of the safest private repositories over the cloud that I have, that I can use. This is one of the most beneficial solutions to be used over the cloud.
We use it for some specific machine learning models to take advantage of the elasticity of the containers. This is the main use of containers. Around 80% of our implementation is on the public cloud, but in some cases, we use a hybrid model. Our clients are large businesses.
I work for a logistics business, so we have a few applications and we apply them to Azure. We pull the codes, stop at the Docker images, and then we push it to the Container for tracking.