>From the testing perspective of iceberg-aws, the existing docker probably suffices. There is https://nvd.nist.gov/vuln/detail/CVE-2025-62506, privilege escalation -but for a short life test-only container, its unimportant, and the management UI isn't needed either.
An older minio version is still needed for testing AWS SDK and third party stores (TestS3FileIOWithLegacyMinIO), On Mon, 2 Mar 2026 at 11:17, Robin Moffatt via dev <[email protected]> wrote: > Hi Steve, > > Thanks for raising this. > There are various options available [1] now that MinIO is not maintained. > For example, I know we previously discussed RustFS [2]. > > I wonder if it's worth a broader consideration of exactly what the Iceberg > project needs here. > This should cover both functionality of a replacement for MinIO, but also > what the replacement project's governance model and longevity/resilience > looks like. > For example, I applaud the fork author's intention with this particular > fork, but they're one person who could easily get a new job/get > bored/overworked, etc, and then we're in the same position again as we are > now. > > thanks, Robin. > > [1]: > https://rmoff.net/2026/01/14/alternatives-to-minio-for-single-node-local-s3/ > [2]: https://lists.apache.org/thread/vnw9jonmfcsz6bwojhfch1nmywyl50h3 > > > On Mon, 2 Mar 2026 at 10:42, Steve Loughran <[email protected]> wrote: > >> >> FYI, someone is promising a new maintained minio fork and docker image >> >> https://blog.vonng.com/en/db/minio-resurrect/ >> >> Seems legititimate enough to be used as a replacement for the current >> minio image for testing; for anything else you'd want to look at the source >> before saving your precious data to it. >> >> Steve >> >
