Migrate Minio from Bitnami to official images
- Dominant language
- Python
- Stars
- 30
- Forks
- 22
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 22
Description
Bitnami is moving to a paid model for its secure containers, and will be deleting their current catalog soon.
This is a breaking change.
We should migrate to the official minio container as soon as possible.
See:
- https://github.com/bitnami/charts/issues/35164
- https://hub.docker.com/r/minio/minio
https://github.com/cisagov/XFD/blob/10c07577272d684f9247dd524187d894b346b249/docker-compose.yml#L59
Contributor guide
Research direction
Start with docker-compose.yml at line 59 and review the official MinIO image documentation linked in the issue. Compare the current Bitnami image configuration with the official image and verify that the compose setup still works after the migration. Done means the Bitnami image is replaced without breaking the MinIO service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100