v-2025-10-13.0

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2025-05-29.0-solr9 or later, then just run:

git fetch --tags origin && \
git checkout v-2025-10-13.0 && \
sudo docker-compose up --build -d

Changes

• Upgrade MusicBrainz Server to v-2025-10-13.0
• Install new command dependency file for MusicBrainz Server scripts (#324)

v-2025-08-11.0

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2025-05-29.0-solr9 or later, then just run:

git fetch --tags origin && \
git checkout v-2025-08-11.0 && \
sudo docker-compose up --build -d

Changes

• Upgrade MusicBrainz Server to v-2025-08-11.0
• Improve and update documentation (#317)
• Update DB_SCHEMA_SEQUENCE for musicbrainz-dev (3cf715c)

v-2025-06-23.0

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2025-05-29.0-solr9 or later, then just run:

git fetch --tags origin && \
git checkout v-2025-06-23.0 && \
sudo docker-compose up --build -d

Changes

• Upgrade MusicBrainz Server to v-2025-06-23.0
• Improve and update documentation (#310, #314)

Reminder

For mirror owners, after last month’s search upgrade, the transition period to switch to Solr 9 will come to an end by the end of the week. That is, the latest Solr 7 search index dumps will be made available on Saturday, 28 June 2025. After that, only the Solr 9 collection backups will be updated.

v-2025-05-29.0-solr9

Breaking changes

This release requires Docker Compose v2 and upgrades MusicBrainz search components with SolrCloud 9, Java 17, Python 3, MusicBrainz XML metaData schema mmd-schema@v-2025-04-23, and MusicBrainz search schema mbsssss@v-2025-05-18.

See the blog post for more details.

Upgrade instructions

The below instructions are for MusicBrainz mirror with enabled replication (and optionally live indexing), adapt these to your own needs.

Assuming that your checked out version of musicbrainz-docker is v-2025-05-23-mbdb30 and that your installed version of Docker Compose is 2, then:

1. Turn off replication (and live indexing if enabled):

   admin/configure rm replication-cron live-indexing-search
   docker compose up -d

2. Switch to the new code with:

   git fetch --tags origin
   git checkout v-2025-05-29.0-solr9

3. Upgrade the services indexer, musicbrainz and search:

   docker compose build
   docker compose up -d

   The search service will drop the previous Solr 7 search indexes when starting.

4. Purge the messages queued for the indexer:

   admin/purge-message-queues

5. Drop the previous Solr 7 search index dumps:

   ( eval $( docker compose config --environment | grep COMPOSE_PROJECT_NAME ) && \
     docker volume rm "${COMPOSE_PROJECT_NAME}_searchdump" )

   It is expected to output the name of the removed volume, usually musicbrainz-docker_searchdump.

6. Set up search indexes (as usual):

   Either build search indexes manually from the installed database:

   docker compose exec indexer python -m sir reindex

   (During our tests it took ~12h with 4 GB memory settings.)

   Or download pre-built search indexes based on the latest data dump:

   docker compose exec search fetch-backup-archives
   docker compose exec search load-backup-archives

   (During our tests it took ~12min after downloading 60 GB of Zstandard-compressed MB Solr backup archives.)

   Once you are satisfied with the search results, drop the fetched archive files:

   docker compose exec search remove-backup-archives

7. (If live indexing was enabled, update its triggers and turn it back on:)

   admin/setup-amqp-triggers uninstall
   admin/setup-amqp-triggers install
   admin/configure add live-indexing-search
   docker compose up -d

8. Turn back on replication:

   admin/configure add replication-cron
   docker compose up -d

What's Changed

• Upgrade search services and requirements by @yvanzo in #306

Full Changelog: v-2025-05-23.0-mbdb30...v-2025-05-29.0-solr9

v-2025-05-23.0-mbdb30

Breaking changes

This release upgrades the MusicBrainz database schema version to 30. It requires to run commands taking down all services during the upgrade.

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

If your musicbrainz-docker is earlier than v-2024-05-13-mbdb29-pg16, 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.

Upgrade instructions

Assuming your checked out version of musicbrainz-docker is v-2024-05-13-mbdb29-pg16 or later, then:

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

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

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

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-2025-05-23.0-mbdb30

4. Upgrade the MusicBrainz database schema:

   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 build musicbrainz
   sudo docker-compose up -d musicbrainz
   sudo docker-compose exec musicbrainz upgrade-db-schema.sh

   The rest of this step took ~12min with 4GB of shared buffers during tests.
   At the end it should say “Done” followed with a message that you can safely ignore as handled already: “UPDATE THE DB_SCHEMA_SEQUENCE IN DBDefs.pm TO 30 !”

   Troubleshooting

   The following lines are expected and can be safely ignored:

   NOTICE:  trigger "…" for relation "…" does not exist, skipping
   

5. This is an optional step. If you had previously built materialized tables, a few of them have to be rebuilt:

   sudo docker-compose exec musicbrainz bash -c 'carton exec -- ./admin/BuildMaterializedTables --database=MAINTENANCE recording_first_release_date artist_release artist_release_group'

6. Load the first replication packet available with the new schema 30:

   sudo docker-compose exec musicbrainz bash -c 'carton exec -- ./admin/replication/LoadReplicationChanges --limit=1'

   and see what it tells you; if the upgrade, it should say “This packet was produced (or begins) at 2025-05-19 18:59:03.681755+00”

   Troubleshooting

   The following lines are expected and can be safely ignored (for the first packet only):

   The current row in musicbrainz.replication_control with key id='1' contains a different value in column current_schema_sequence (30) than the replication packet suggests it should have as the old value (29). at /musicbrainz-server/admin/replication/ProcessReplicationChanges line 497.
   WARNING:  amqp could not commit tx mode on broker 1, reply_type=2, library_errno=4
   

7. Turn cron jobs back on:

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

8. Restart all services:

   sudo docker-compose up -d musicbrainz

Changes

• Upgrade MusicBrainz Server to v-2024-05-23.0-schema-change (release notes)
• Now fetch the event-art-archive dump too

P.S. Search upgrades will occur in a separate release.

v-2025-05-20.0-mbdb30

Erratum

This release upgrades MusicBrainz Server to v-2024-05-19.0-schema-change. Unfortunately, this version has bugs related to the schema change.

Since then, these bugs have been fixed in MusicBrainz Server v-2024-05-23.0-schema-change and the release v-2025-05-23.0-mbdb30, see release notes.

v-2025-05-05.0

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2024-05-13-mbdb29-pg16 or later, then just run:

git fetch --tags origin && \
git checkout v-2025-05-05.0 && \
sudo docker-compose up --build -d

Only change

• Upgrade MusicBrainz Server to v-2025-05-05.0

v-2025-04-14.0

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2024-05-13-mbdb29-pg16 or later, then just run:

git fetch --tags origin && \
git checkout v-2025-04-14.0 && \
sudo docker-compose up --build -d

Only change

• Upgrade MusicBrainz Server to v-2025-04-14.0

v-2025-03-24.0

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2024-05-13-mbdb29-pg16 or later, then just run:

git fetch --tags origin && \
git checkout v-2025-03-24.0 && \
sudo docker-compose up --build -d

Only change

• Upgrade MusicBrainz Server to v-2025-03-24.0

v-2025-02-24.0

Update instructions

Assuming your checked out version of musicbrainz-docker is v-2024-05-13-mbdb29-pg16 or later, then just run:

git fetch --tags origin && \
git checkout v-2025-02-24.0 && \
sudo docker-compose up --build -d

Only change

• Upgrade MusicBrainz Server to v-2025-02-24.0