Thanks, folks! Great points! I do like the idea of using something other than MinIO.
My only 2 cents: For the quickstart docker compose file, I believe that we should use object storage that can be automatically configured without having to put in credentials. The goal of the quickstart is to have anyone who has Docker running locally to be able to launch a non-production version of Polaris through a single command. It's targeted for users who are just learning about Polaris. So, in my opinion, this rules out AWS S3. As long as we meet that criteria, I do think that changing would be appropriate. Thanks for bringing this up! Go community, Adam On Thu, Jan 8, 2026 at 9:16 AM Dmitri Bourlatchkov < [email protected]> wrote: > Hi All, > > Apache Ozone works well, AFAIK [1] but it certainly requires more setup > work than MinIO. > > WDYT about RustFS? [2] > > [1] > > https://polaris.apache.org/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-ozone/ > > [2] https://github.com/rustfs/rustfs > > Cheers, > Dmitri. > > On Thu, Jan 8, 2026 at 8:46 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > Hi Yong, > > > > Thanks for bringing this to our attention. > > > > I agree with your assessment regarding the recent changes to MinIO OSS. > We > > could evaluate Apache Ozone as a potential alternative; while STS might > > require more changes, I believe it’s worth investigating. > > > > In the short term, we could update the quickstart guide to use AWS S3 > while > > we wait to finalize the Ozone integration. > > About Ceph, that's a good idea, assuming we have the same kind of > > layout/experience. > > > > Regards, > > JB > > > > On Thu, Jan 8, 2026 at 7:49 AM Yong Zheng <[email protected]> wrote: > > > > > Hello, > > > > > > We have MinIO support as S3 compatible storage and this is great as it > > > allows users to quickly test out Apache Polaris as a catalog and write > > to a > > > S3 compatible storage. However, as MinIO is now under maintenance mode > > only > > > for OSS (https://github.com/minio/minio?tab=readme-ov-file), we won't > be > > > able to get updated images from public image registry, should we > consider > > > switch our primary getting-start example to non-MinIO one instead (the > > > current one is MinIO as backend: > > > > > > https://github.com/apache/polaris/blob/main/getting-started/quickstart/docker-compose.yml > > )? > > > Without doing so, users will be likely pulling down outdated MinIO > images > > > with critical CVEs couple months later for their local setup to play > > > around. If using outdated MinIO is a concern as the getting-start > > example, > > > maybe we should switch to the Ceph one ( > > > > > > https://github.com/apache/polaris/blob/main/getting-started/ceph/docker-compose.yml > > ) > > > but updated it to match the same layout? > > > > > > Thanks, > > > Yong Zheng > > > > > >
