The recommended method of upgrading from 2.1 to 2.2 is to dump and restore your database. If you are using the docker-compose/standalone deployment, this can be done by the following method.

NOTE that this assumes your running docker-compose configuration is under the standalone directory.

• First, dump your current database to the default import location and IMMEDIATELY shut down the service:

cd contrib/docker-compose/standalone
cp .env .env.bak
echo "PGP_EXPORT=standalone_pgp_import" >> .env
./clean-sks-dump.bash
./create-sks-dump.bash
docker-compose down
mv .env.bak .env

• Delete your existing db and ptree (double check the actual names of your volumes, they may differ!):

docker volume rm standalone_pg_data standalone_hkp_data

• Now upgrade and start up:

git pull && git checkout branch-2.2
./mksite.bash
docker-compose build
docker-compose up -d

• Check for progress:

docker-compose logs --tail=100 -f hockeypuck

You should see lots of warnings as it ingests and normalises the dump. This is normal.