Upgrade path from 2.0.8.1_beta_2024-05-07 to the latest version

Support
1

Hi

We run 2.0.8.1_beta_2024-05-07 as a Docker container on an Ubuntu Docker host. We want to upgrade to the latest version. We have the following questions:

  • We want to use stable builds only. Which is the latest version for our setup?
  • How to upgrade? On Release v2.1.0.5_stable_2025-03-04 · duplicati/duplicati · GitHub it’s mentioned that “automatic upgrade is not supported”. Docker images can not be updated by other means then shutting down the container, removing the image, pulling the image for the new version and start the container again. What do you mean with “automatic updates are not supported” in our setup? Do we have to upgrade via intermediate versions?
  • Anything else to be considered?

Thanks in advance for all help.

2

You can use the latest or stable tag, which is updated only on stable releases.

The “no automatic upgrade” does not relate to Docker. The v2.0.x versions had an automatic updater built in, which we could not easily port, so for 2.1+ there is currently only an update checker, but updates need to be manually installed.

Each version will automatically upgrade your databases to the latest version, so there are no other steps required for upgrades. Simply install the latest version and it will upgrade anything that needs to be upgraded. This covers all versions, so you can upgrade from 2.0.0.0 to 2.1 in a single step.

For Docker, upgrade is easy, simply pull the latest image and run.

Downgrading sometimes requires a manual step to revert the database changes before installing an older version, but a database tool is included in the install.

We try very hard to make upgrades seemless and well tested, so everything should just work after the upgrade, but some options may have been removed, and there may be edge cases we have not encountered before.

3

@kenkendk Great, thank you very much for your quick response.

4

Using Duplicati from Docker gives hints on things you might not already do.
Especially when skipping versions, see release notes for what got changed.
v2.1.0.4_stable_2025-01-31 (you now need to use a password for the GUI).
v2.2.0.0_stable_2025-10-23
I’m pointing to the initial “stable”. Later small updates tend not to repeat info.
IMO changes at major releases (e.g. 2.x to 2.y) ought to be easier to locate.

2 Likes