Private docker registry

Siddu Lavula 0 Reputation points
2024-04-11T20:11:35.6366667+00:00

How to integrate the my private docker registry with Azure.

Where can i place private docker registry and test the connection ?

I want use my docker registry instead of ACR.

Docker registry hosted one of physical server (not in Azure)

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
396 questions
{count} votes

2 answers

Sort by: Most helpful
  1. v-vvellanki-MSFT 3,895 Reputation points Microsoft Vendor
    2024-04-11T21:10:27.5966667+00:00

    Hi @Siddu Lavula,

    Thanks for contacting Microsoft Q&A platform.

    Answer would depend on whether you are trying to container service in azure or Kubernetes service in azure (AKS).

    In case of container service, you can pass registry information in the az container create command using parameters --registry-login-server, --registry-username and --registry-password. --image is fetched using registry-server specified there.

    In case of AKS, the mechanism would vary in case there is static credentials or dynamic credentials. You can read about how to configure k8s to fetch images from private registry here.

    Hope this helps you.

    0 comments No comments

  2. Luis Arias 4,871 Reputation points
    2024-04-11T21:41:14.0733333+00:00

    Hi Siddu Lavula,

    In general to integrate your Physical server to be consume from Azure services, you have two option:

    1. Publish your docker registry service on physical server to be consumed from public, this could include adding network rules on firewall or updating the configuration for public facing services on your physical network.
    2. Second options is by integrating privately the physical network to Azure services by Virtual Network Services, here some options that you can use:
      1. Azure Migrate: Azure Migrate is a tool that helps you migrate machines as physical servers to Azure. This can be useful for migrating on-premises physical servers or VMs virtualized by platforms such as Xen and KVM
      2. Azure Network Adapter: Azure Network Adapter can be used to connect an on-premises standalone server to Azure virtual networks. This creates a secured virtual connection over the internet, extending your on-premises network into Azure
      3. Site-to-Site VPN or ExpressRoute: On-premises resources can access resources in a virtual network using private IP addresses over a Site-to-Site VPN (VPN Gateway) or ExpressRoute. This allows you to securely connect your on-premises network to your Azure VNet

    In both cases after setup the network communications you can configure the registry information as mention v-vvellanki-MSFT.

    References:

    Cheers

    Luis

    0 comments No comments