Skip to content

fix(langfuse): run MinIO from Chainguard's public image - #134

Merged
tarannum-2002 merged 1 commit into
developmentfrom
fix/235-langfuse-minio-image
Nov 7, 2026
Merged

tarannum-2002 merged 1 commit into
developmentfrom
fix/235-langfuse-minio-image

Conversation

@tarannum-2002

Copy link
Copy Markdown
Contributor

What

Inside the langfuse chart, MinIO now runs Chainguard's public build, cgr.dev/chainguard/minio, pinned to the digest the Langfuse on the dev VM runs. It runs as user 65532 with a matching fsGroup. It creates the langfuse bucket as a directory before the server starts, the way the VM does it, and the bucket-init Job is off. Chart 3.0.1 to 3.0.2.

Why

MinIO no longer lets anyone pull its images without logging in: quay.io/minio/minio and docker.io/minio/minio both answer 401. On dev, Langfuse's MinIO pod is stuck in ImagePullBackOff:

failed to resolve reference "quay.io/minio/minio:latest": unexpected status from HEAD request ... 401 UNAUTHORIZED

The bucket-init Job uses minio/mc from the same place, so it would fail the same way. Langfuse needs only its one bucket to exist.

Testing

  • Pulled each candidate without logging in:
    • quay.io/minio/minio:latest and docker.io/minio/minio (including the last release tag) answer 401;
    • cgr.dev/chainguard/minio, both latest and the pinned digest, answers 200.
  • Ran the pinned image locally with this exact command as user 65532: MinIO came up ready, the langfuse bucket was listed over S3, and an upload to it succeeded.
  • Rendered the chart with dev's values: the MinIO Deployment uses the pinned image with 65532 and fsGroup 65532, and there is no bucket-init Job.

charts/minio (the knowledge-provider's) has the same quay.io default. It is not changed here, since nothing runs it on dev.

Relates to OpenAgriNet/engineering-tracker#235

@tarannum-2002
tarannum-2002 merged commit 22eb53e into development Nov 7, 2026
1 check passed
@tarannum-2002
tarannum-2002 deleted the fix/235-langfuse-minio-image branch November 7, 2026 17:16
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.

1 participant