0 0 Share PDF

Upgrade to DTR 2.5.0 failure

Article ID: KB000769

Issue

After upgrading to DTR 2.5.0, the dtr-scanningstore-<containerid> container (docker/dtr-postgres:2.5.0) keeps restarting. Looking at the container logs, you see this repeated:

FATAL: database files are incompatible with server 
DETAIL: The data directory was initialized by PostgreSQL version 9.6, which is not compatible with this version 10.3. 
time="..." level=warning msg="error starting postgres" error="exit status 1" 

Prerequisites

The upgrade was performed in the following order:

  1. Upgraded Docker engine from 17.06.2-ee-7 to 17.06.2-ee-8

  2. Upgraded UCP from 2.2.7 to to 3.0.0

  3. Upgraded DTR from 2.4.3 to 2.5.0:

    docker run -it --rm docker/dtr upgrade --ucp-insecure-tls 
    

The upgrade completed without any errors.

Resolution

This is a known issue, and a fix is outlined in the DTR 2.5 release notes. It is described at the section under Known Issues that begins with Docker EE Advanced Features:

https://docs.docker.com/ee/dtr/release-notes/#250-2017-4-17

The resolution is to remove the scanningstore container and the dtr-postgres volume, and perform a reconfigure:

docker stop dtr-scanningstore-$replica 
docker rm dtr-scanningstore-$replica 
docker volume rm dtr-postgres-$replica 
docker run --rm -it docker/dtr:2.5.0 reconfigure ...

Also, re-download the CVE Database by clicking the download cve db button in DTR UI.