Skip to content

fix(security): bind MinIO ports to 127.0.0.1 by default#13

Merged
oldhero5 merged 1 commit into
mainfrom
fix/minio-bind-localhost
May 24, 2026
Merged

fix(security): bind MinIO ports to 127.0.0.1 by default#13
oldhero5 merged 1 commit into
mainfrom
fix/minio-bind-localhost

Conversation

@oldhero5

Copy link
Copy Markdown
Owner

Summary

  • Bind MinIO's S3 API (9000) and console (9001) to 127.0.0.1 by default via ${MINIO_BIND:-127.0.0.1} so the dev-default minioadmin/minioadmin credentials are not reachable from the LAN.
  • Document the MINIO_BIND=0.0.0.0 override in .env.example and docs-site/docs/deployment/docker.md for users who need LAN access.

Closes #10

Test plan

  • docker compose --profile apple config shows host_ip: 127.0.0.1 on both 9000 and 9001 by default.
  • MINIO_BIND=0.0.0.0 docker compose --profile apple config shows host_ip: 0.0.0.0 (override works).
  • In-container access via the waldo-net bridge is unaffected (other services still hit minio:9000 / mc alias set waldo http://minio:9000).
  • CI test workflow green.

The default docker-compose published MinIO's S3 API (9000) and console
(9001) on 0.0.0.0 with the dev-default minioadmin/minioadmin
credentials, exposing the object store to anyone on the LAN. Bind both
ports to 127.0.0.1 by default via ${MINIO_BIND:-127.0.0.1}; users who
need LAN access can set MINIO_BIND=0.0.0.0 in .env. Documented the
override in .env.example and docs-site/docs/deployment/docker.md.

Closes #10

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@oldhero5
oldhero5 merged commit 59a075d into main May 24, 2026
1 check passed
@oldhero5
oldhero5 deleted the fix/minio-bind-localhost branch May 24, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bind MinIO ports to 127.0.0.1 (security default)

1 participant