• /
  • EnglishEspañolFrançais日本語한국어Português
  • Log inStart now

Install Synthetics for Dual Stack using Docker

This guide covers the infrastructure validation, Docker daemon configuration, and image deployment required to support Dual Stack (IPv4 and IPv6) testing in your private location environment using Docker.

Prerequisites

Before you begin, ensure you have the following:

Validate your infrastructure

Before proceeding, verify that your host machine and network are configured for Dual Stack networking.

Test IPv6 connectivity by running ping6 ipv6.google.com or ping -6 ipv6.google.com, or the equivalent command for your machine.

Important

If the ping fails, ensure your VPC, subnet, and security groups are configured to allow IPv6 traffic before continuing with this installation. Your environment must support both IPv4 and IPv6 for Dual Stack operation.

Verify Docker is ready for Dual Stack

Ensure your Docker installation is configured to handle both IPv4 and IPv6 traffic. To verify that Docker has IPv6 enabled, run:

bash
$
docker info | grep -i ipv6

The output should confirm that IPv6 is enabled. If it is not, refer to the Docker documentation to enable Dual Stack support before proceeding.

Launch the Synthetics job manager

The Dual Stack-enabled runtime images are publicly available on Docker Hub and will be pulled automatically by the job manager. Run the Synthetics job manager container with your private location key:

Tip

Replace <YOUR_PRIVATE_LOCATION_KEY> with your actual private location key from the New Relic UI.

bash
$
docker run \
>
-e PRIVATE_LOCATION_KEY=<YOUR_PRIVATE_LOCATION_KEY> \
>
-d \
>
--restart unless-stopped \
>
-v /var/run/docker.sock:/var/run/docker.sock:rw \
>
newrelic/synthetics-job-manager

The Synthetics job manager will now be running with Dual Stack support enabled, allowing your monitors to test both IPv4 and IPv6 endpoints.

Verify installation

To confirm your Synthetics job manager is running correctly:

  1. Check the container status:

    bash
    $
    docker ps
  2. View the job manager logs:

    bash
    $
    docker logs <container_id>
  3. In the New Relic UI, go to one.newrelic.com > All capabilities > Synthetic monitoring > Private locations and verify your private location shows as healthy.

What's next?

After setting up your Dual Stack-enabled private location, you can:

Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.