build: switch to Soldevelo container images (Bitnami access now paid)

[jkondrat-sd]

Switch container base images to SolDevelo

Bitnami images now require a VMware Tanzu subscription (change effective August 28, 2025). This causes pipeline failures and added cost for teams that relied on the public registry.

SolDevelo provides drop-in replacements - same Debian-based images, same startup scripts, same environment-variable API - built openly from SolDevelo/containers and tagged to match Bitnami upstream.

Image substitutions

• bitnami/minio:2024 → soldevelo/minio:2024.12

Summary by Sourcery

Enhancements:

• Replace the MinIO container image with the SolDevelo equivalent to maintain self-hosted deployments without Bitnami registry access.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The deployment switches MinIO from the Bitnami container image to the matching SolDevelo image, preserving the existing Compose configuration while removing reliance on Bitnami’s newly restricted public registry access.

File-Level Changes

Change	Details	Files
Replace the MinIO service’s Bitnami base image with the SolDevelo drop-in equivalent to avoid Bitnami registry access and subscription requirements.	Update the MinIO image reference to the SolDevelo image tagged for the corresponding upstream release. Leave the service configuration, environment variables, and startup behavior unchanged.	selfhosted/servers/minio/docker-compose.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 2 issues

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="selfhosted/servers/minio/docker-compose.yml" line_range="4" />
<code_context>

   minio-s3:
-    image: bitnami/minio:2024
+    image: soldevelo/minio:2024.12
     container_name: minio
     hostname: minio
</code_context>
<issue_to_address>
**Rocket.Chat still needs Bitnami access**

When teams deploy Rocket.Chat after Bitnami access becomes subscription-gated and do not have that access, docker Compose still pulls Bitnami MongoDB for the Rocket.Chat stack, so deployments without the required registry access fail to start that service.

Replace the Rocket.Chat MongoDB image with an accessible equivalent, or explicitly limit the stated migration scope to MinIO.
</issue_to_address>

### Comment 2
<location path="selfhosted/servers/minio/docker-compose.yml" line_range="4" />
<code_context>

   minio-s3:
-    image: bitnami/minio:2024
+    image: soldevelo/minio:2024.12
     container_name: minio
     hostname: minio
</code_context>
<issue_to_address>
**README points to old image**

When users follow the MinIO reference in the README, the README still links to Bitnami’s MinIO page, so users looking up the configured image are sent to the old Bitnami image instead of the SolDevelo replacement.

Update the README MinIO reference to point to the SolDevelo image.
</issue_to_address>

Sourcery assessment

Needs a human reviewer. 1 finding to address first, and the replacement MinIO image may handle the existing data volume differently or write data that the old image cannot use; reverting the image would not necessarily undo changes already made to stored objects. A compatibility failure could also take the storage service offline.

Blocking findings: selfhosted/servers/minio/docker-compose.yml:4

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

🟠 High · Rocket.Chat still needs Bitnami access

When teams deploy Rocket.Chat after Bitnami access becomes subscription-gated and do not have that access, docker Compose still pulls Bitnami MongoDB for the Rocket.Chat stack, so deployments without the required registry access fail to start that service.

Replace the Rocket.Chat MongoDB image with an accessible equivalent, or explicitly limit the stated migration scope to MinIO.

Prompt for AI agents

In `selfhosted/servers/minio/docker-compose.yml` at line 4:

**Rocket.Chat still needs Bitnami access**

When teams deploy Rocket.Chat after Bitnami access becomes subscription-gated and do not have that access, docker Compose still pulls Bitnami MongoDB for the Rocket.Chat stack, so deployments without the required registry access fail to start that service.

Replace the Rocket.Chat MongoDB image with an accessible equivalent, or explicitly limit the stated migration scope to MinIO.

[sourcery-ai]

⚪ Low · README points to old image

When users follow the MinIO reference in the README, the README still links to Bitnami’s MinIO page, so users looking up the configured image are sent to the old Bitnami image instead of the SolDevelo replacement.

Update the README MinIO reference to point to the SolDevelo image.

Prompt for AI agents

In `selfhosted/servers/minio/docker-compose.yml` at line 4:

**README points to old image**

When users follow the MinIO reference in the README, the README still links to Bitnami’s MinIO page, so users looking up the configured image are sent to the old Bitnami image instead of the SolDevelo replacement.

Update the README MinIO reference to point to the SolDevelo image.