Repository navigation
feat(chainguard-forks): add MinIO RELEASE.2026-11-16T00-11-40Z - #466
Conversation
…from the Chainguard fork
There was a problem hiding this comment.
The changes that are a consequence of changing the base image, sound a lot like potentially breaking changes.
We already have two chainguard-base images in our registry, for example registry.sighup.io/fury/minio:RELEASE.2026-07-17T12-07-51Z-chainguard.
Can we verify if those images were already affected by these changes, or if they have been introduced just lately? If that's the case, it might be reasonable to add an additional suffix to the tagged image to express the base image change (ie. registry.sighup.io/fury/minio:RELEASE.2026-11-16T00-11-40Z-chainguard-wolfi).
If needed, you can check the commit where the chainguard MinIO images sync was removed from the modules/chainguard-forks/images.yml
…uard-wolfi suffix
|
Thanks! |
Description
Add MinIO image built from the Chainguard fork, tag RELEASE.2026-11-16T00-11-40Z → registry.sighup.io/fury/minio:RELEASE.2026-11-16T00-11-40Z-chainguard, and document the fork in modules/chainguard-forks/README.md.
Notes
The runtime base is now wolfi-base instead of minio/minio. The entrypoint, sh, bash and mc are the same, with these differences:
Tests