The `createbuckets` service in docker-compose.base.yml has been failing on
every local `docker compose up`, so the modelshare and images buckets are
never created. It uses two mc subcommands that no longer exist:
mc config host add -> mc alias set
mc policy set -> mc anonymous set
The image is unpinned (`minio/mc`), so this broke silently whenever upstream
dropped them. On mc RELEASE.2025-08-13T08-35-41Z the container exits 1 with:
mc: <ERROR> `config` is not a recognized command.
Because the entrypoint is a single `&&` chain, the first failure aborts it and
neither bucket is made. Nothing else in the stack reports a problem, so the
failure is easy to miss until something tries to use object storage.
Also add `--ignore-existing` to both `mc mb` calls. Without it the fix would
only work once: `mc mb` on an existing bucket exits 1 ("you already own it"),
which aborts the same `&&` chain, so the service would go back to failing on
the second and every subsequent `docker compose up`.
Verified against a running local MinIO:
- before: container exits 1, `mc ls` shows no buckets
- after: exits 0, both buckets created and set public
- re-run: exits 0 again (idempotent)
- control: `mc mb` on an existing bucket is rc=1 without the flag, rc=0 with it
Zachary Lowden