Skip to content

How is vScope Updated?

vScope offers automatic updates to minimize maintenance efforts and ensure your installation is always up to date. Automatic updates are the default and recommended option. You can manage your update settings under Settings > Software.

vScope running in Docker or Kubernetes does not update itself. Update it by replacing the container image, see Docker and Kubernetes.

To enable automatic updates:

  1. Navigate to Settings > Software.
  2. Toggle Automatic update to “On”.
  3. Choose your preferred update behavior:
    • At night (default) – Updates are installed during off-hours.
    • Immediately – Updates are applied as soon as they are available.
    • Upon restart – Updates are installed when vScope service restarts.

If you want to control when updates are applied:

  1. Disable Automatic update under Settings > Software.
  2. Download the latest vScope installer from vscope.net/download.
  3. Follow the installation instructions to manually update your vScope instance.

In a container, the vScope program files are part of the image and only /data is kept on the volume. vScope therefore does not install updates itself, and the Automatic update setting has no effect. To update, start a new container from the new image with the same volume. Your data, settings and license are kept in the volume.

Each release is published both as latest and with its version number, for example vscope:3.40.0. Use a version tag if you want to decide when to update and get the same version when the container is recreated.

  1. Pull the new image:

    Terminal window
    docker pull europe-docker.pkg.dev/isl-vscope/release/vscope:latest
  2. Stop and remove the container. vScope can take a few minutes to shut down; --stop-timeout 330 in the run command gives it time to finish.

    Terminal window
    docker stop vscope-server
    docker rm vscope-server
  3. Start it again with the same docker run command and options as before, including ports, memory, JAVA_OPTS and the vscope-data volume mounted at /data. See Install vScope.

Discovery proxies in Docker are updated the same way, with the vscope-proxy image and the proxy’s own volume. See Discovery proxies.

  • With the latest tag and imagePullPolicy: Always, restart the deployment to pull the new image:

    Terminal window
    kubectl rollout restart deployment/vscope-server -n default
  • With a version tag, change the tag in the manifest and apply it again with kubectl apply -f vscope-server.yaml.

Discovery proxies are updated the same way with deployment/vscope-proxy.

🔗 Check the latest vScope releases