Repository navigation
fix(langfuse): run MinIO from Chainguard's public image - #134
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 matchingfsGroup. It creates thelangfusebucket 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/minioanddocker.io/minio/minioboth answer 401. On dev, Langfuse's MinIO pod is stuck in ImagePullBackOff:The bucket-init Job uses
minio/mcfrom the same place, so it would fail the same way. Langfuse needs only its one bucket to exist.Testing
quay.io/minio/minio:latestanddocker.io/minio/minio(including the last release tag) answer 401;cgr.dev/chainguard/minio, bothlatestand the pinned digest, answers 200.langfusebucket was listed over S3, and an upload to it succeeded.fsGroup65532, and there is no bucket-init Job.charts/minio(the knowledge-provider's) has the samequay.iodefault. It is not changed here, since nothing runs it on dev.Relates to OpenAgriNet/engineering-tracker#235