-
Notifications
You must be signed in to change notification settings - Fork 554
fix: resolve registry image conflict in docker-compose #114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: resolve registry image conflict in docker-compose #114
Conversation
Issue: links directive was failing on podman - Removed unsupported 'links' directive for Podman compatibility
yshngg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
|
Please merge this or i do need to do anything else for merging. |
|
Hi @toby , review complete, merge please 🙏 ! |
domdomegg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you 🙌
domdomegg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(reapproving after fixing merge conflicts)
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Issue: links directive was failing on podman - Removed unsupported 'links' directive for Podman compatibility <!-- Provide a brief summary of your changes --> It was failing on Podman because Podman doesn't support the links directive that Docker Compose does, and we already using depends_on, which establishes the dependency relationship between services; we can simply remove the links section from your docker-compose.yml file. ## Motivation and Context docker-compose -links deprecated #107 Fix the defect by removing link. ## How Has This Been Tested? Yes. Test by running on both. For Docker run. docker build -t registry . docker compose up For Podman podman build -t registry . podman compose up ## Breaking Changes Yes for podman. ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ x] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ x] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [x ] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [ x] My code follows the repository's style guidelines - [ x] New and existing tests pass locally - [ x] I have added appropriate error handling - [x ] I have added or updated documentation as needed ## Additional context It is related to issue #107 Co-authored-by: Avinash Sridhar <[email protected]> Co-authored-by: adam jones <[email protected]>
Issue: links directive was failing on podman
It was failing on Podman because Podman doesn't support the links directive that Docker Compose does, and we already using depends_on, which establishes the dependency relationship between services; we can simply remove the links section from your docker-compose.yml file.
Motivation and Context
docker-compose -links deprecated #107
Fix the defect by removing link.
How Has This Been Tested?
Yes. Test by running on both.
For Docker run.
docker build -t registry .
docker compose up
For Podman
podman build -t registry .
podman compose up
Breaking Changes
Yes for podman.
Types of changes
Checklist
Additional context
It is related to issue #107