Upgrading from a previous version

AI Tools

Upgrading from a previous version on Unix-based deployments

Preliminary notes

Upgrading is usually a two-step process:

  1. upgrade the mdssc package by installing the newer package

  2. upgrade the existing code by downloading new images

Acquire the installer package

In order to acquire the new package please visit My OPSWAT -> Product Downloads

Warning

Installing the new package removes all MetaDefender Software Supply Chain containers and images from the machine. Named volumes (database data) and /etc/mdssc/customer.env are preserved. On an offline machine, stage the offline toolkit archive before you install the package.

Debian / Ubuntu package (.deb)

  1. Back up before upgrading

sudo mdssc -u export_db # writes /etc/mdssc/db_<...>.tar sudo mdssc -u export_settings

  1. Update packages (online installations only)

sudo apt-get update

  1. Move to the folder containing the installer and install it

sudo dpkg -i <name of the file>.deb || sudo apt-get install -f

For an offline installation, use the following form instead:

sudo dpkg -i ./mdssc-<VERSION>.deb

  1. Update images (online installations only) — this pulls images from the container registry. For offline installations, see "Offline (air-gapped) upgrade" below.

sudo mdssc -u update

  1. Optionally, you can check the status using the following command:

sudo mdssc -c status

  1. Open a browser and navigate to the web interface: http://<server> to configure your deployment

Red Hat Enterprise Linux / CentOS package (.rpm)

  1. Back up before upgrading

sudo mdssc -u export_db # writes /etc/mdssc/db_<...>.tar sudo mdssc -u export_settings

  1. Update packages (online installations only)

sudo yum -y update

  1. Move to the folder containing the installer and install it

sudo yum upgrade <name of the file>.rpm

  1. Update images (online installations only) — this pulls images from the container registry. For offline installations, see "Offline (air-gapped) upgrade" below.

sudo mdssc -u update

  1. Optionally, you can check the status using the following command:

sudo mdssc -c status

  1. Open a browser and navigate to the web interface: http://<server> to configure your deployment

Offline (air-gapped) upgrade

Before you begin, transfer both files to the offline machine: the release RPM and the offline toolkit archive of the same version. Extract the toolkit before installing the RPM — installing the RPM removes the currently installed containers and images, and without the toolkit already on disk there is nothing left to start.

tar -xzf mdssc-offline-<VERSION>.tar.gz sudo yum upgrade -y --disablerepo="*" ./mdssc-<VERSION>.noarch.rpm cd mdssc-offline-<VERSION> sudo ./mdssc.sh -u load_images sudo mdssc -c start sudo mdssc -c status

Do not run sudo yum -y update or sudo mdssc -u update on an offline machine — both require internet access.

Next to read:
Kubernetes deployment
null
On This Page
Upgrading from a previous versionUpgrading from a previous version on Unix-based deploymentsPreliminary notesAcquire the installer packageDebian / Ubuntu package (.deb)Red Hat Enterprise Linux / CentOS package (.rpm)Offline (air-gapped) upgrade