Skip to content
This repository has been archived by the owner on Aug 20, 2020. It is now read-only.

Port collision handling #33

Open
bitbrain opened this issue Apr 19, 2016 · 0 comments
Open

Port collision handling #33

bitbrain opened this issue Apr 19, 2016 · 0 comments

Comments

@bitbrain
Copy link
Contributor

A port collision will occur when starting at least two containers with an exposed port in common. As a result at least one container will not start with an error message like:

docker: Error response from daemon: driver failed programming
external connectivity on endpoint dock-<formula> (<id>): 
Bind for 0.0.0.0:<port> failed: port is already allocated.

Failed to start the Docker container.

To solve this issue, formulas could provide information about their exposed ports and an "interface" to set a custom port. dock could then look up for collisions in order to assign a free port number to the respective container before they get started.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant