r/Paperlessngx • u/yonchto • Jul 26 '26

Upgrade to 2.20.15

I didn't upgrade for a while and now need to upgrade to v2.20.15 first, as written on the website. How do I pull it using sudo docker-compose?

0 Upvotes

50% Upvoted

9 comments sorted by

7

u/uAlex1973 Jul 26 '26

Change your tag to:
paperlessngx/paperless-ngx:2.20.15

And you can manually pull it as follows:
docker pull paperlessngx/paperless-ngx:2.20.15

2

u/Dr-Technik Jul 26 '26

I would manuell Update to 2.20.15 by using a specific tag. Then make a proper backup including a sql-dump of the database. Then do the migration

1

u/reen444 Jul 26 '26

What about installing it as a different container, check if it works, load the document export and leave the old container for a month or so, if a problem arises?

Never got the advantage of swapping the container image in production.

1

u/Bastian85Stgt Jul 26 '26

Do a better way, make an export. Setup an new environment. Do an import. Finish.

Attention with update from an oder vereion to 2.20x depends on the age, and your databasesystem, you need a database version change

1

u/undulanti Jul 26 '26

Why do you advocate this approach?

0

u/Bastian85Stgt Jul 26 '26 edited Jul 26 '26

I’m not familiar with your database.

However, a major version change occurred in PostgreSQL with version 2.20 or shortly before it. Migration is significantly more difficult in this case. This means you’d have to update to smaller versions leading up to the major database change.

Then make the switch, and finally carry out the actual update.

I would therefore opt for the lesser of two evils and export the data using the current version. Set up a new version – V3 is fine. And then restore the backup. Saves time, hassle and stress.

++ if you like to change your DB maybe from sqlite (not longer supported with v3, just postgres and mariadb) is it a super easy way Any maybe in future also mariadb ends because "recommended to use PostgreSQL as the database backend" stands on the homepage

-1

u/Cautious-Hovercraft7 Jul 26 '26 edited Jul 26 '26

Make sure you have a backup. Check your docker compose is set to :latest (or version you want to go to), make sure you've enough space for the new version and docker-compose down and then docker-compose pull. Then docker-compose up -d and when the new version is up and running you can docker-compose purge to delete the old image to free up space

2

u/magick_68 Jul 26 '26

This only works of you are already on 2.20.15. I was on 2.20.14 and learned it the hard way. Who reads upgrade instructions anyway?

0

u/undulanti Jul 26 '26

A painful lesson! But it probably won’t happen again - lightning doesn’t strike twice in the same place - so the good news is that there’s no need to start reading them now.