---
title: "Updating Lacuna PSC on Docker"
description: "Updating an on-premises Lacuna PSC on Docker: image tags, reading the changelog and handling database model changes when several containers are running."
canonical: "https://docs.lacunasoftware.com/en-us/articles/psc/on-premises/docker/update"
locale: "en"
product: "PSC"
last_updated: "2026-11-17"
---

# Updating Lacuna PSC on Docker

To update an [on-premises](https://docs.lacunasoftware.com/en-us/articles/psc/on-premises) instance of [Lacuna PSC](https://docs.lacunasoftware.com/en-us/articles/psc) on Docker, follow the steps below.

The Docker image is available on Docker Hub:

**[Lacuna PSC Docker Image](https://hub.docker.com/r/lacunasoftware/psc)**

The image to use is `lacunasoftware/psc:1.7.5`. Use the explicit version tag when updating, so you know exactly which version your container runs.

## Updating guidelines

Back up the database before updating.

Then, before updating your container, check the [Changelog](https://docs.lacunasoftware.com/en-us/articles/psc/changelog) to see what has changed from your current version to the one you are installing. To know how to check the installed version, see [this article](https://docs.lacunasoftware.com/en-us/articles/psc/on-premises/check-version).

If any of the versions included in the update have database model changes ("Updates database model: yes") then you should proceed carefully, as the container will attempt to update the database upon startup.

In this scenario, if you run more than one container, it is recommended to choose one of the following options:

* Reduce the number of running containers to 1.
* Allow only one container to update the database. This is done by adding the following setting to all but one container:

```sh
General__AutoUpdateDatabase=false
```

> **Note**
>
> A container with this setting does not start while the database model is out of date. Start it only after the container that updates the database has started.

Finally, pull the image with the tag corresponding to the desired version:

```sh
docker pull lacunasoftware/psc:1.7.5
```

Then stop and remove the running container:

```sh
docker stop <name>
docker rm <name>
```

Run the original `docker run` command again, with the same settings (environment variables or env file) and volumes, but pointing to the tag `1.7.5`. If you use Docker Compose, change the image tag in the compose file and run `docker compose up -d`.

To roll back, restore the database backup and recreate the container from the previous image tag.

## See also

* [Checking the version of Lacuna PSC](https://docs.lacunasoftware.com/en-us/articles/psc/on-premises/check-version)
* [Running Lacuna PSC without db_owner privileges](https://docs.lacunasoftware.com/en-us/articles/psc/on-premises/unprivileged-db-user)
* [Lacuna PSC command-line tool](https://docs.lacunasoftware.com/en-us/articles/psc/on-premises/tool)
* [Changelog](https://docs.lacunasoftware.com/en-us/articles/psc/changelog)
