---
title: "<span class=\"command\">docker push</span> setup"
description: This page describes the legacy CDM implementation, which will be deprecated in an upcoming release. We strongly recommend that you transition to the current CDM implementation as soon as possible.
component: forgeops
version: 7.2
page_id: forgeops::legacy/cdm/aks/setup/push
canonical_url: https://docs.pingidentity.com/forgeops/7.2/legacy/cdm/aks/setup/push.html
section_ids:
  next_step: Next step
---

# docker push setup

|   |                                                                                                                                                                                                                                       |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | This page describes the legacy CDM implementation, which will be deprecated in an upcoming release. We strongly recommend that you transition to [the current CDM implementation](../../../../cdm/overview.html) as soon as possible. |

In the deployment environment you're setting up, Skaffold builds Docker images using the Docker software you've installed on your local computer. After it builds the images, Skaffold pushes them to a Docker registry available to your AKS cluster. With the images on the remote Docker registry, Skaffold can orchestrate the Ping Identity Platform, creating containers from the Docker images.

For Skaffold to push the Docker images:

* Docker must be running on your local computer.

* Your local computer needs credentials that let Skaffold push the images to the Docker repository available to your cluster.

* Skaffold needs to know the location of the Docker repository.

Perform the following steps to let Skaffold to push Docker images to a registry accessible to your cluster:

1. If it's not already running, start Docker on your local computer. For more information, see the Docker documentation.

2. If you don't already have the name of the container registry that will hold ForgeRock Docker images, obtain it from your Azure administrator.

3. Log in to your container registry:

   ```
   $ az acr login --name registry-name
   ```

   Azure repository logins expire after 4 hours. Because of this, you'll need to log in to ACR whenever your login session expires \[[1](#_footnotedef_1 "View footnote.")].

4. Run the kubectx command to obtain the Kubernetes context.

5. Configure Skaffold with your Docker repository location and Kubernetes context:

   ```
   $ skaffold config \
     set default-repo registry-name.azurecr.io/cdm -k my-kubernetes-context
   ```

   For example:

   ```
   $ skaffold config set default-repo my-container-registry.azurecr.io/cdm -k small
   ```

## Next step

You've completed all the setup tasks for AKS. Now you're ready to deploy the platform in your new cluster:

* [icon: check-square-o, set=fa][Become familiar with the CDM](../../intro.html)

* [icon: check-square-o, set=fa][Understand CDM architecture](../../architecture.html)

* [icon: check-square-o, set=fa][Set up your local environment and create a cluster](../../setup-cdm.html)

* [icon: square-o, set=fa]*[Deploy the platform](../../deploy.html)*

* [icon: square-o, set=fa][Access platform UIs and APIs](../../access.html)

* [icon: square-o, set=fa][Plan for production deployment](../../next-steps.html)

***

[1](#_footnoteref_1). You can automate logging in to ACR by using the cron utility.