Update your private probe in Docker

Before you make any changes, you can recover your current configuration from the running container:

• Run docker ps and identify the container that is running solarwinds/synthetics-private-probe.

• Run docker inspect CONTAINER_ID and review the Env section to see the values for SYNTHETICS_COLLECTOR_URL, API_TOKEN, LOCAL_ID, NAME, and LOG_LEVEL.

How is Docker upgraded?

A typical Docker upgrade goes as follows.

1. Execute the docker ps command to find the running private probe container.

   docker ps 

2. Stop and remove the private probe container.

   docker stop CONTAINER_ID
   docker rm CONTAINER_ID

3. Pull the new image.

   docker pull solarwinds/synthetics-private-probe:latest

4. Start a new container using the same environment variables and the same LOCAL_ID as before.

Update your Configuration file

• If you started the probe using environment variables, stop the existing container and start a new one with updated docker run parameters.

• If you use a configuration file, edit the YAML file and restart the container so it picks up changes.

To keep the same probe identity and checks, do not change LOCAL_ID. Using the same LOCAL_ID tells SolarWinds Observability that this is the same probe instance, just redeployed.

Pull a newer image (recommended)

1. Execute the following command in Docker to pull a newer Docker image.

   docker pull solarwinds/synthetics-private-probe:latest

2. Restart the container using the new image tag (:latest or a specific version).

   If you need to pin to a specific version or roll back later, you can use a tagged image like solarwinds/synthetics-private-probe:v1.0.2 instead of :latest.