Upgrade DPA on a Docker daemon platform
Complete the following tasks to upgrade DPA running on a Docker daemon platform:
- Stop the running container of the existing DPA version
- Back up the DPA repository database and configuration folders
- Download the file containing the new DPA version and load the image
- Run the new DPA docker container with the same Persistent Volume Claims folder
- Remove the stopped container that includes the older version of DPA
Stop the running container of the existing DPA version
-
Run the following command to list the ID of the DPA container:
docker container ls -
Run the following command to to stop the DPA container:
docker stop CONTAINER_ID
Keep the stopped container as it is until the new container is running successfully.
Back up the DPA repository database and configuration folders
Back up the existing repository and the configuration, log, and licensing files on the persistent volume claim (PVC). In case the upgrade is unsuccessful, the backup copies can be used to revert to the older version of DPA.
When the new DPA container starts, it detects that the existing files and repository correspond to an earlier version. It immediately updates the files to correspond to the new version. 1.
-
Back up the DPA repository database.
-
Copy the following folders from the PVC and save the copies in a different location to back up logs, configurations, and licensing:
ignite_configconflogslicensing
Download the file containing the new DPA version and load the image
-
Open the SolarWindsCustomer Portal.
-
Download the
tar.gzfile that holds the new DPA Docker container image. The file name is similar to the following, where nnnn.n.n.n represents the version number:SolarWinds-DPA-Image-nnnn.n.n.n.tar.gz -
Run the following command to load the image from the
tar.gzfile:docker load < FILENAMEFor example:
docker load < SolarWinds-DPA-Image-2025.4.0.512.tar.gz -
After you run the
docker loadcommand, verify that the image is loaded by running the command to list Docker images:docker imagesThe list of images should include
solarwinds/dpa.
Run the new DPA docker container with the same Persistent Volume Claims folder
The Persistent Volume Claims folder must be the same one used for the previous version. If it is not, DPA configuration data will be lost and the container will be treated as a new installation.
When the new DPA container starts, it detects that the existing files and repository correspond to an earlier version. It immediately updates the files to correspond to the new version.
Depending on the operating system, complete one of the following tasks:
- Run the container on a Linux OS
- Run the container on a Windows OS
Run the container on a Linux OS
If the computer has a Linux OS, run the following command:
docker run -v /usr/dpa/conf:/opt/dpa/iwc/tomcat/conf/ -v /usr/dpa/ignite_config:/opt/dpa/iwc/tomcat/ignite_config/ -v /usr/dpa/logs:/opt/dpa/iwc/tomcat/logs/ -v /usr/dpa/licensing:/opt/dpa/iwc/tomcat/licensing/ -p 443:8124 -d IMAGE_NAME/dpa:IMAGE_VERSION
For example:
docker run -v /usr/dpa/conf:/opt/dpa/iwc/tomcat/conf/ -v /usr/dpa/ignite_config:/opt/dpa/iwc/tomcat/ignite_config/ -v /usr/dpa/logs:/opt/dpa/iwc/tomcat/logs/ -v /usr/dpa/licensing:/opt/dpa/iwc/tomcat/licensing/ -p 443:8124 -d solarwinds/dpa:2025.4.0.512
Run the container on a Windows OS
If the computer has a Windows OS, run the following command:
docker run -v "C:\PATH\conf":/opt/dpa/iwc/tomcat/conf/ -v "C:\PATH\ignite_config":/opt/dpa/iwc/tomcat/ignite_config/ -v "C:\PATH\logs":/opt/dpa/iwc/tomcat/logs/ -v "C:\PATH\licensing":/opt/dpa/iwc/tomcat/licensing/ -p 443:8124 -d IMAGE_NAME/dpa:IMAGE_VERSION
For example:
docker run -v "C:\Program Files\SolarWinds\DPA\iwc\tomcat\conf":/opt/dpa/iwc/tomcat/conf/ -v "C:\Program Files\SolarWinds\DPA\iwc\tomcat\ignite_config":/opt/dpa/iwc/tomcat/ignite_config/ -v "C:\Program Files\SolarWinds\DPA\iwc\tomcat\logs":/opt/dpa/iwc/tomcat/logs/ -v "C:\Program Files\SolarWinds\DPA\iwc\tomcat\licensing":/opt/dpa/iwc/tomcat/licensing/ -p 443:8124 -d solarwinds/dpa:2025.4.0.512
Remove the stopped container that includes the older version of DPA
When the new DPA container is running successfully, run the following command to remove the old container:
docker rm CONTAINER_ID