Big Bear Tech World Releases MinIO Docker Image (Built from Source)

BigBearBlog
1

We’re excited to announce that Big Bear Tech World now publishes an official Docker image for MinIO, built directly from the MinIO source. This image addresses the recent shift in MinIO’s distribution model (source-only) and provides a secure, multi-architecture container that’s ready for both development and production.

Why this image?

  • Built from source: MinIO moved to a source-only distribution. Our build reproduces the official release from source so you can run trusted, up-to-date MinIO images.

  • Multi-architecture: Images are built for both linux/amd64 and linux/arm64 so they run on laptops, servers, and ARM-based devices.

  • Security-focused: The image runs MinIO as a non-root user, includes sensible defaults, and ships with health checks for reliable orchestration.

  • CI/CD automation: We’ve implemented a GitHub Actions workflow to automatically detect new MinIO releases, build multi-arch images, run tests, and publish to Docker Hub.

Quick Start

From the Apps/minio directory:


# Development

docker-compose -f compose/docker-compose.dev.yml up -d

# Production

cp config/.env.example .env

# edit .env to set secure MINIO_ROOT_USER / MINIO_ROOT_PASSWORD

docker-compose -f compose/docker-compose.prod.yml up -d

Pull the image directly:


# Latest (development)

docker pull bigbeartechworld/big-bear-minio:latest

# Pin to a specific MinIO release (recommended for production)

docker pull bigbeartechworld/big-bear-minio:RELEASE.2025-10-15T17-29-55Z

CI/CD Notes

  • Workflow: .github/workflows/build_and_release_for_minio.yaml

  • Behavior: Weekly checks for new MinIO releases, manual dispatch available, and builds on push when Apps/minio/** changes.

  • Tags published: latest, the specific MinIO release tag (e.g., RELEASE.2025-...), and a git-sha trace tag.

Security & Hardening

  • The container runs MinIO as an unprivileged user by default. You can override MINIO_UID/MINIO_GID in the env if necessary.

  • The default credentials in the compose files are intentionally easy for local testing—please update them in production (config/.env.example).

  • For production, enable TLS by mounting certificates into /data/.minio/certs/.

Contribution & Support

If you find issues or want improvements, open a GitHub Issue or submit a PR. We’ll monitor MinIO upstream releases and keep the build scripts up-to-date.

Thanks for using Big Bear Tech World’s MinIO Docker image. Happy storing! :bear:

1 Like