Skip to main content
Skip table of contents

Updating Images Addresses to Use ACR

LAST UPDATED: MAR 24, 2025

To migrate the agent and executor containers, update the Docker Compose configuration to reference the Azure Container Registry.


Updating the Image Address

Template docker-compose.yml
YAML
version:
services:
  d3agent:
    image: "d3soar.azurecr.io/d3prod/d3agent:<D3 vSOC version>"
    restart: always
    environment:
      - REMOTE_SERVER_URL=<D3 vSOC URL>
      - PROXY_IDENTITY=<D3 vSOC Agent Security Token>
      - PYTHON_REMOTE_URL=http://<Docker Host IP>:<Docker Host Port>/
      - PYTHON_REMOTE_GUID=<Executor Identifier>
      - SERVICE_DISPLAY_NAME=<Proxy Agent Display Name>
      - DOCKER_GID=<Docker Group ID>
      - DOCKER_PORT=<Docker Host Port>
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
  
  d3executor:
    image: "d3soar.azurecr.io/d3prod/d3executor:<D3 vSOC version>"
    ports:
      - "<Docker Host Port>:9090"
    restart: always
    environment:
      - EXECUTOR_GUID=<Executor Identifier>

Modify the image field in docker-compose.yml:

Before (Google Container Registry)

EXAMPLE D3 AGENT IMAGE (OLD)

YAML
gcr.io/nimble-cortex-285618/d3prod/d3agent:16.8.409.0

EXAMPLE D3 EXECUTOR IMAGE (OLD)

YAML
gcr.io/nimble-cortex-285618/d3prod/d3executor:16.8.409.0
After (Azure Container Registry)

EXAMPLE D3 AGENT IMAGE (NEW)

YAML
d3soar.azurecr.io/d3prod/d3agent:16.8.409.0

EXAMPLE D3 EXECUTOR IMAGE (NEW)

YAML
d3soar.azurecr.io/d3prod/d3executor:16.8.409.0

Performing the Migration

  1. Stop the running containers.

    BASH
    docker compose stop  
  2. Pull the updated images from ACR.

    BASH
    docker compose pull  
  3. Recreate the containers with the new images.

    BASH
    docker compose up -d --force-recreate  
  4. Verify the migration by checking the container logs.

    BASH
    docker logs {container_id}  

Migration is successful if the logs contain:

  • "Starting server"

  • "heartbeat successful"

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.