Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 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 |
| pS[port] = struct{}{} | ||
| pb[port] = []network.PortBinding{{HostIP: localhost}} |
There was a problem hiding this comment.
there was an issue in the docker client itself in the past where there was some overlap of ports, but it was supposed to be fixed here so allowing the docker engine to choose should now be safe again.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #209 +/- ##
========================================
+ Coverage 8.20% 9.18% +0.98%
========================================
Files 87 87
Lines 6317 6371 +54
========================================
+ Hits 518 585 +67
+ Misses 5707 5687 -20
- Partials 92 99 +7 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Overview
There has been a recurring issue with duplicate port allocations, it seems like there was a bug in the most recent "fix", looking at the release notes for the docker engine here it looks like by allowing docker to assign a port itself, it will no longer collide so we should be able to remove all the locks and safeguards we had in place around it.
The exception is when re-creating containers. (stopping/starting) they are now preserved, so existing references to those ports remain valid.
Ran test multiple times, all passing.