Skip to content

feat(chainguard-forks): add MinIO RELEASE.2026-11-16T00-11-40Z - #466

Merged
edobarre merged 3 commits into
mainfrom
feat/add-chainguard-minio
Nov 18, 2026
Merged

edobarre merged 3 commits into
mainfrom
feat/add-chainguard-minio

Conversation

@edobarre

@edobarre edobarre commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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:

  • curl is not available: use busybox that is now included.
  • MC_CONFIG_DIR is not set: when the container runs as a non-root user without a writable home, mc cannot save its config. Pass --config-dir /tmp/.mc or set MC_CONFIG_DIR=/tmp/.mc.
  • The MINIO_ROOT_USER_FILE, MINIO_ROOT_PASSWORD_FILE and MINIO_CONFIG_ENV_FILE variables are not set, so the credentials are not read from files under /run/secrets: pass MINIO_ROOT_USER / MINIO_ROOT_PASSWORD as environment variables.
  • EXPOSE 9000 and WORKDIR / are not set: declare the ports in the Pod spec and use absolute paths for data, certificates and keys. The working directory defaults to / .

Tests

  • Dry-run of sync.sh OK.
  • Image built locally from Dockerfile.dev and tested on a local cluster: S3, SFTP, LDAP (AD), health and metrics endpoints OK.

@edobarre edobarre changed the title feat(chainguard-forks): add MinIO RELEASE.2026-11-16T00-11-40Z built … feat(chainguard-forks): add MinIO RELEASE.2026-11-16T00-11-40Z Nov 18, 2026

@davide-rossi-ce davide-rossi-ce left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@edobarre

edobarre commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor Author

Thanks!
I checked the two images already in the registry: both RELEASE.2026-05-20T23-44-52Z-chainguard and RELEASE.2026-07-17T12-07-51Z-chainguard were built on the old minio/minio base, and thus are not affected by these changes.
Only the images built from fork tag RELEASE.2026-09-21T00-15-41Z onwards use the new wolfi-base.
I agree that the same -chainguard suffix would hide the base change, so I updated the tag in the new commit to RELEASE.2026-11-16T00-11-40Z-chainguard-wolfi

@davide-rossi-ce davide-rossi-ce left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@edobarre
edobarre merged commit 147be54 into main Nov 18, 2026
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants