Description
I'm using MinIO for local development, as a drop-in replacement for S3 (my goal is to test an S3 client), and my end goal would be to automate making the bucket I created with mc mb public, so that my application does not need credentials to work locally.
Expected behavior
When using mc anonymous , I should see some changes in the console UI regarding access, either in the anonymous section, or in the summary section
Actual behavior
There are no changes in the UI, and when trying to download a file programmatically, I get a 403. When I try using the UI to set the access to "public", it works.
Steps to reproduce the behavior
I have this container:
# compose.yaml
services:
minio:
image: minio/minio:RELEASE.2025-04-22T22-12-26Z
volumes:
- /myminio
command: server myminioI use this to log into the container: docker compose exec minio /bin/bash
Then, I create a bucket:
mc mb myminio/my-bucket
mc: Configuration written to `/tmp/.mc/config.json`. Please update your access credentials.
mc: Successfully created `/tmp/.mc/share`.
mc: Initialized share uploads `/tmp/.mc/share/uploads.json` file.
mc: Initialized share downloads `/tmp/.mc/share/downloads.json` file.
Bucket created successfully `myminio/my-bucket`.I can then see that bucket in the Console UI.
Then I try to make that bucket public:
bash-5.1# mc anonymous set public myminio/my-bucket
Access permission for `myminio/my-bucket` is set to `public`mc --version
mc version RELEASE.2025-04-16T18-13-26Z (commit-id=b00526b153a31b36767991a4f5ce2cced435ee8e)
Runtime: go1.24.2 linux/amd64
Copyright (c) 2015-2025 MinIO, Inc.
License GNU AGPLv3 <https://www.gnu.org/licenses/agpl-3.0.html>