Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jkondrat-sd wants to merge 1 commit into
base: master
Choose a base branch
from
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion selfhosted/servers/minio/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
services:

minio-s3:
image: bitnami/minio:2024
image: soldevelo/minio:2024.12

@sourcery-ai sourcery-ai Bot Oct 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 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 sourcery-ai Bot Oct 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ 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.

container_name: minio
hostname: minio
environment:
Expand Down
Loading