chore(compose): pin app images to v2.0.0-rc.2 instead of latest - #647
Merged
Conversation
The compose stack referenced linagoraai/openrag:latest and linagoraai/openrag-admin-ui:latest. On Docker Hub 'latest' for openrag still points at the old v1.1.13 GA image, and openrag-admin-ui has no 'latest' tag at all — so 'docker compose up' either pulls a stale v1 image or fails outright. Pin both to the current published v2 tag (v2.0.0-rc.2) for a reproducible, correct pull.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request updates container image tags in the Docker Compose configuration, pinning both the openrag API template and admin-ui service from ChangesDocker Compose Image Version Bump
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 task
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
Pin the two application images in
infra/compose/docker-compose.yamlto the current published v2 tag instead of the floatinglatest:linagoraai/openrag:latest→linagoraai/openrag:v2.0.0-rc.2linagoraai/openrag-admin-ui:latest→linagoraai/openrag-admin-ui:v2.0.0-rc.2Why
latestis unsafe for this branch:linagoraai/openrag:lateststill points at the old v1.1.13 GA image (the last release built frommain) — the v2 RC pipeline never tagslatest.linagoraai/openrag-admin-uihas nolatesttag at all.So
docker compose up(without--build) today either pulls a stale v1 image or fails on the missing admin-ui tag. Pinning tov2.0.0-rc.2— the latest tag actually published for this branch — makes the pull reproducible and correct.Notes
build:sections are unchanged, so localdocker compose up --buildstill builds from source.v2.0.0once the GA image is published (no such tag exists on Docker Hub yet).Summary by CodeRabbit