---
title: Starting the gateway instance in a Docker container
description: Use the Docker command that you copied from PingOne to start a Docker container. Run the Docker container on a computer that can reach your LDAP directory and PingOne.
component: pingone
page_id: pingone:integrations:p1_starting_gateway_instance_docker_ldap
canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_starting_gateway_instance_docker_ldap.html
revdate: August 22, 2024
section_ids:
  about-this-task: About this task
  before-you-begin: Before you begin
  steps: Steps
  next-steps: Next steps
---

# Starting the gateway instance in a Docker container

## About this task

Use the Docker command that you copied from PingOne to start a Docker container. Run the Docker container on a computer that can reach your LDAP directory and PingOne.

## Before you begin

* If you have a valid gateway credential, have it ready. Alternatively, you can create a new credential on the **Overview** tab in the gateway details. Learn more in [Creating or deleting a gateway credential](https://docs.pingidentity.com/pingone/integrations/p1_creating_deleting_gateway_credential_ldap.html)

* Ensure that Docker is installed and the Docker Engine is running.

## Steps

1. In the PingOne admin console, go to **Integrations → Gateways** and locate the appropriate gateway.

2. Click the gateway name to expand the gateway details.

3. Click the **Download** tab.

4. In the **Standalone** section, review the prerequisites and instructions.

5. In the **Instructions** section, copy the Docker command and paste it into a file or the command prompt.

6. If you agree to the terms of the license agreement, open the Docker command in a text editor and change `-e PING_IDENTITY_ACCEPT_EULA=no` to `-e PING_IDENTITY_ACCEPT_EULA=yes`.

7. Optional: To configure an LDAP Gateway client application to use a forward web proxy server to handle traffic between the gateway and PingOne, add access information to the Docker command.

   * `-e http_proxyHost=<HTTP_PROXY_HOST>`

   * `-e http_proxyPort=<HTTP_PROXY_PORT>`

   * `-e http_proxyUser=<HTTP_PROXY_USER>`

   * `-e http_proxyPassword=<HTTP_PROXY_PASSWORD>`

   * `-e http_proxyAuthenticationMethod=DIGEST (or BASIC)`

     `http_proxyHost` and `http_proxyPort` are required to use a web proxy. `http_proxyUser`, `http_proxyPassword`, and `http_proxyAuthenticationMethod` are required if the web proxy requires authentication.

     |   |                                                                                                                                                                                                                                                                                                   |
     | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
     |   | For `http_proxyAuthenticationMethod`, it's worth noting that BASIC (as in basic authentication) transmits access credentials without encryption. You should use DIGEST (as in digest authentication) because it uses a challenge-response mechanism and does not send the password in plain text. |

     |   |                                                                                                                                                                                                                                                                                                                                                                             |
     | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
     |   | * You must configure the web proxy settings per each running instance. For example, if you're running two gateway client applications, you must configure web proxy settings in both instances.

     * Digest authentication does not support international characters.

     * Basic authentication requires configuration in the proxy server to support international characters. |

8. At a command prompt, run the Docker command.

## Next steps

[Verify a gateway instance](p1_verifying_gateway_instance_ldap.html)