---
title: "Core Linux Update"
slug: "clone-quality-modeller-core-linux-update"
description: "How to carry out the Test Modeller Core Linux Update."
tags: ["Test Modeller", "Installation"]
updated: 2025-04-03T14:40:19Z
published: 2025-04-03T14:40:19Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.curiositysoftware.ie/llms.txt
> Use this file to discover all available pages before exploring further.

# Core Linux Update

## 1 - Backup All Data Stores

See our page on[**Quality Modeller Maintenance**](/docs/test-modeller-maintenance) to make sure that the postgres and neo4j databases are backed and stored securely.

Optionally, you may want to back up the docker images as well, in case you need to roll back the update.

---

## 2 - Backup Old Files

If the previous installation was uzipped in a folder that contains the version name, for example:

/opt/curiosity/1.16.2

Then you already have a backup of config. If you did not use the version, then you should back up the files in the package folder.

---

## 3 - Copy New Version Onto Linux Filesystem

Unzip the latest version of Quality Modeller into /opt/curiosity/[version number].

```shell
unzip dockerDeployment_1.17.0 -d /opt/curiosity/1.17.0
```

---

## 4 - Copy Configuration

Usually it should be enough to simply copy over the **.env** file and the **docker-compose-custom.yml** file (if it exists) over from the previous install. If you have a new license, this is the time to put it into the **.env** file.

There is a script in the **utils** subfolder to copy and merge these files automatically, given the **package**folder of the old version:

```shell
# assuming we are in the package folder of the new release 
# the -s parameter points to the package folder of the old release
./utils/copy-config.sh -s ../../7.20.0/package
```

Some custom installs may have involved changes to other files such as nginx config.

Make sure that any config files are copied over to the new application folder.

---

## 5 - Changes in The Docker-Compose File

Normally there are no changes in the docker compose file. If there are, there will be special instructions for that version upgrade.

---

## 6 - Start The New Version

The exact command will depend on what was used during the initial installation. In most cases it will be:

```shell
sudo ./run.sh
```

If you get the error "ERROR: The Compose file './docker-compose -f docker-compose-fullstack.yml up' Unsupported config option for services.modeller_job_engine: 'init'. Then you need to remove the 'init' line from the docker file in the 'job_engine' section.

## 7 - Legacy Update Method (Optional)

The steps detailed above describe the process for updating Quality Modeller from version **2.25.0** and above. If you have an older version of Quality Modeller and are updating to **2.25.0** or above, the Curiosity team will usually help with migrating to this new process. However, if for some reason the old method of updating the **docker-compose-fullstack-*.yml** files is required, the Quality Modeller **package**folder will have a **legacy** subfolder which contains the old **docker-compose-fullstack-*.yml** files****and the old version of the **run.sh** script. You can edit those files and start the services by first navigating to this **legacy** subfolder:

```shell
cd legacy
sudo ./run.sh
```

## Related

- [Quality Modeller](/get-started-with-test-modeller.md)