Skip to main content

Upgrading Informer (Linux w/ Docker)

note

The current version of Informer 5 is version 2026.1.5

Upgrading a Docker installation means pointing your docker-compose.yml at newer Informer images, pulling them, and restarting. Read through this guide once before starting. If you have questions, contact Informer Support at i5support@entrinsik.com.

Prerequisites​

Check plugin compatibility first

If you use plugins, contact Support to verify compatibility with your target Informer version before upgrading.

  • PostgreSQL 16 is required as of Informer 5.9.0. See Migrating from PostgreSQL 11 to PostgreSQL 16 (Linux w/ Docker) in the Database maintenance section before upgrading if you are still on PostgreSQL 11.
  • Verify the host server meets the recommended System requirements.
  • Verify that a ./pgdata directory exists and is populated in your installation directory. If it is not, stop and follow the ./pgdata Folder Creation (Linux w/ Docker) guide in the Database maintenance section first, or you risk data loss.
  • Verify that the user performing the upgrade has root access and is a member of the docker group. If not, prepend sudo to the commands below.
  • Ensure each Informer service in docker-compose.yml (informer-api, informer-query, informer-schedules) has the entrypoint and stop_grace_period that 2026.1.5 and later expect (note the index.js path may change between releases):
entrypoint: "/bin/sh -c 'node dockerpreboot.js && exec pm2 start node_modules/@entrinsik/informer-server/index.js -i 2 --name informer --kill-timeout 40000 --no-daemon'"
stop_grace_period: 45s

When an Informer process stops, it first finishes the work it already started and records that it stopped cleanly, which can take up to 30 seconds. exec hands Docker's stop signal straight to pm2, --kill-timeout 40000 gives each Informer process 40 seconds before pm2 forces it, and stop_grace_period: 45s gives pm2 that long before Docker forces the container. A process forced to quit before it finishes is recorded as not cleanly stopped. Once PostgreSQL shows no database session for it, Informer retires that record on its own, about 30 seconds after the process last checked in. Behind a connection pooler that shares database sessions between processes, automatic retirement is turned off and an administrator retires the record by hand; contact Informer Support for the procedure.

Upgrading from a very old release

If you are upgrading from Informer 5.0.19 or earlier, the database must be migrated from PostgreSQL 9 before you proceed, or you risk data loss. Contact Informer Support for the correct migration path for your version before upgrading.

Back up Informer​

Back up the Informer metadata before upgrading. See the Backups and Restores (Linux w/ Docker) guide in the Database maintenance section.

Upgrade Informer​

  1. Stop all Informer components: 
    docker-compose stop
  2. Delete the current Informer containers. Using the default naming, these are: 
    docker-compose rm informer-api
    docker-compose rm informer-query
    docker-compose rm informer-schedules
  3. Edit docker-compose.yml and set the image line under every Informer section to the target version, substituting your version for x.y.z (for example, 2025.1.1): 
    image: docker.entrinsik.com:5000/informer:x.y.z
    By default these services are named informer-api, informer-query, and informer-schedules.
  4. Pull the latest versions of the containers: 
    docker-compose pull
  5. Start everything back up with the start script: 
    ./start.sh