metabrainz/musicbrainz-docker v-2023-05-15.1-mbdb28

on GitHub

Breaking changes

This release upgrades to MusicBrainz database schema 28. It requires to run commands taking down musicbrainz service during the upgrade.

If your musicbrainz-docker is earlier than v-2022-05-17-mbdb27, you must first update to it (see its release notes) and follow the upgrade instructions below, or remove everything using sudo docker-compose down --rmi local --volumes and reinstall.

Disk space requirement has been slightly readjusted: 200 GB (or 100 GB without indexed search), system included.

Upgrade instructions

Assuming your checked out version of musicbrainz-docker is v-2022-05-17-mbdb27 or later, then:

1. Ensure you’ve replicated up to the most recent replication packet available with the old schema 27. If you’re not sure, run:

   sudo docker-compose exec musicbrainz bash -c ./admin/replication/LoadReplicationChanges

   and see what it tells you; if you’re ready to upgrade, it should say “This replication packet matches schema sequence #\28, but the database is currently at #\27.”

2. Turn off cron jobs:

   admin/configure rm replication-cron
   sudo docker-compose up -d musicbrainz

3. Switch to the new code with:

   git fetch --tags origin
   git checkout v-2023-05-15.1-mbdb28
   sudo docker-compose build

4. Upgrade the database schema (it may take a while to vacuum at the end, ignore the ending message about DB_SCHEMA_SEQUENCE):

   mkdir -p local/compose/ && cp -a admin/lib/upgrade-db-schema/musicbrainz-stopped.yml local/compose/
   admin/configure add local-compose-musicbrainz-stopped
   sudo docker-compose up -d musicbrainz
   sudo docker-compose exec musicbrainz upgrade-db-schema.sh

1. Turn cron jobs back on:

   admin/configure rm local-compose-musicbrainz-stopped
   admin/configure add replication-cron

2. Restart all services:

   sudo docker-compose up -d musicbrainz

Only change

• Upgrade MusicBrainz Server to v-2023-05-15-schema-change (release notes)