Central Port registry to preserve docker container ports on reboot #94
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.
When a server reboots all the dynamic port mappings from Docker get reset leading to 502 bad gateway errors in Nginx, or even worse: the wrong servers displaying for different host names.
This PR addresses the issue in #82
It creates a new upstart service called
dokku-ports.conf
which is run afterdocker
which exposes a simple HTTP service that keeps track of the next freedocker
port.The
dokku
script can then ask this service for the next service and then bind it directly upon container creation, rather than a dynamic binding.The next available port is stored in
~git/port
. Upon startup the service checks the ports on all the running docker containers, and makes sure that the next port won't conflict with any running containers.This is an alternative to rewriting the
nginx.conf
files in this alternative pull request