Update docker.io/tootsuite/mastodon Docker tag to v4.5.0

Update docker.io/tootsuite/mastodon Docker tag to v4.5.0
Photo by Rolf van Root / Unsplash

Patch update of container without any issue by means of Docker compose YAML infrastructure and automated Portainer GitOps workflow with dependency update facilitated by Mend's Renovate Bot.

This MR contains the following updates:

Package Update Change
docker.io/tootsuite/mastodon minor v4.4.8 -> v4.5.0

Release Notes

mastodon/mastodon (docker.io/tootsuite/mastodon)

v4.5.0

Compare Source

Mastodon

For a user-focused highlight of these changes, see https://blog.joinmastodon.org/2025/11/mastodon-4.5/
For changes of particular interest to application developers, see https://blog.joinmastodon.org/2025/10/mastodon-4-5-for-devs/
For a more detailed run-down on the changes, see the Changelog section below!

Upgrade overview

This release contains upgrade notes that deviate from the norm:

:warning: The minimum supported version for Redis has been bumped to 7.0
:warning: The minimum supported version for PostgreSQL has been bumped to PostgreSQL 14
:warning: Rolling updates from versions earlier than Mastodon 4.3 are not supported
:warning: Import jobs from Mastodon versions earlier than Mastodon 4.2 are not supported
ℹ️ Sidekiq has been updated, which may require you to change health check or monitoring code
ℹ️ Requires streaming server restart
ℹ️ Requires database migrations

For more information, view the complete release notes and scroll down to the upgrade instructions section.

Changelog

Added
Changed
Fixed
Removed

Upgrade notes

To get the code for v4.5.0, use git fetch && git checkout v4.5.0.

[!NOTE]
As always, make sure you have backups of the database before performing any upgrades. If you are using docker-compose, this is how a backup command might look: docker exec mastodon_db_1 pg_dump -Fc -U postgres postgres > name_of_the_backup.dump

Dependencies

External dependencies have changed since v4.4.0, with the Redis and PostgreSQL minimum version being higher.

  • Ruby: 3.2 or newer
  • PostgreSQL: 14 or newer
  • Elasticsearch (recommended, for full-text search): 7.x (OpenSearch should also work)
  • LibreTranslate (optional, for translations): 1.3.3 or newer
  • Redis: 7.0 or newer
  • Node: 20 or newer
  • libvips (optional, instead of ImageMagick): 8.13 or newer
  • ImageMagick (optional if using libvips): 6.9.7-7 or newer
Sidekiq update and health checks

We have updated Sidekiq from Sidekiq 7 to Sidekiq 8, but the health check we used to provide in docker-compose.ymlspecifically checks for Sidekiq 7. If you use docker-compose.yml from the release, it has already been updated. But if you copied or adapted the old health check, you will need to update it to test for Sidekiq 8.

Instead of the following line:

test: ['CMD-SHELL', "ps aux | grep '[s]idekiq\ 7' || false"]

It should read:

test: ['CMD-SHELL', "ps aux | grep '[s]idekiq\ 8' || false"]
Update steps

The following instructions are for updating from 4.4.8.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations. If you are upgrading from a pre-4.3 version, please fully update to Mastodon 4.3 first or stop all Mastodon processes before updating, and please have a look at the “Ongoing import jobs from Mastodon 4.1 and earlier” section of Mastodon 4.4.0's release notes if you are updating from a pre-4.2 version.

Non-Docker

[!TIP]
The charlock_holmes gem may fail to build on some systems with recent versions of gcc.
If you run into this issue, try BUNDLE_BUILD__CHARLOCK_HOLMES="--with-cxxflags=-std=c++17" bundle install.

  1. If you are using rbenv:
    1. update the list of available versions
    2. then, install the proper Ruby version by doing RUBY_CONFIGURE_OPTS=--with-jemalloc rbenv install in the Mastodon install directory (e.g. /home/mastodon/live)
  2. Install dependencies with bundle install and yarn install --immutable
  3. Precompile the assets: RAILS_ENV=production bundle exec rails assets:precompile
  4. Run the database migrations: RAILS_ENV=production bundle exec rails db:migrate
  5. Restart all Mastodon processes.
When using Docker
  1. Run the database migrations: docker-compose run --rm web bundle exec rails db:migrate
  2. Restart all Mastodon processes.
Update steps from a Mastodon 4.5 pre-release

The following instructions are for updating from a Mastodon 4.5 pre-release (4.5.0-beta.1, 4.5.0-beta.2, 4.5.0-rc.1, v4.5.0-rc.2 or v4.5.0-rc.3). See the section above if you are updating from an older version.

Non-Docker

[!TIP]
The charlock_holmes gem may fail to build on some systems with recent versions of gcc.
If you run into this issue, try BUNDLE_BUILD__CHARLOCK_HOLMES="--with-cxxflags=-std=c++17" bundle install.

  1. Install dependencies with bundle install and yarn install --immutable
  2. Precompile the assets: RAILS_ENV=production bundle exec rails assets:precompile
  3. Run database migrations: RAILS_ENV=production bundle exec rails db:migrate
  4. Restart all Mastodon processes.
When using Docker
  1. Run database migrations: RAILS_ENV=production bundle exec rails db:migrate
  2. Restart all Mastodon processes.

Read more

Me on Mastodon - This link is here for verification purposes.