fix: Podman compatibility by adding environment configurable repository prefix to Docker Compose image references#2002
fix: Podman compatibility by adding environment configurable repository prefix to Docker Compose image references#2002Vchen7629 wants to merge 1 commit into
Conversation
…or private repo compatibility Signed-off-by: vchen7629 <[email protected]>
|
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)
WalkthroughUpdated ChangesDocker image path qualification
Estimated code review effort: 1 (Trivial) | ~3 minutes Related issues: Suggested labels: 🚥 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 |
Summary
Port of PR #1919 to target main instead of release-0.5.1 branch, Fixes #1206. Podman fails to resolve unqualified image names (no registry prefix) by default, causing
podman pull/podman compose upto fail with:Error: short-name "langflowai/openrag-backend:latest" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"Changes
docker-compose.ymlwith Added environment variable prefix that defaults todocker.io/(5 images total: opensearch, opensearch-dashboards, backend, frontend, langflow) if none providedTesting
podman compose upnow succeeddocker composestill works identically (fully-qualifieddocker.io/...and unqualified...resolve to the same image on Docker Hub)Summary by CodeRabbit