Performing a Manual Agent Update
LAST UPDATED: AUGUST 21, 2025
When the version of the D3 vSOC platform changes, the Linux agent is not automatically upgraded. If the update includes a change to the major version, the agent must also be updated to the same major version to maintain compatibility and ensure proper functionality. Minor or patch updates to vSOC may not require an agent update, depending on the nature of the platform changes.
Procedure
To update the Linux agent, follow these steps:
Back up the existing docker-compose.yml file.
Modify the docker-compose.yml file by replacing the existing version number at the end of the image fields (i.e., d3agent:
<old_version>
and d3executor:<old_version>
) with 17.3.4.YAMLservices: d3agent: image: "d3soar.azurecr.io/d3prod/d3agentn8:17.4.2" 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:17.4.2" privileged: true ports: - "<Docker Host Port>:9090" restart: always environment: - EXECUTOR_GUID=<Executor Identifier>
Run the following command to recreate the d3agent container:
BASHdocker compose up -d --force-recreate
Verify that the agent is connected in the Agent Management dashboard.