Retry fetching mapped host port when a container is created #14
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.
I've been running into a race condition where the host port mapping is not available right after a container is created. Attempting to inspect the container too quickly results in a JSON blob that looks roughly like:
which in turn results in the following exception:
I see this error very frequently with the
ResourcesReaper
container, but I don't think it's specific to that. Retrying after a small delay seems to consistently resolve the problem. This PR implements retry logic for all calls toDocker.Containers.mapped_port/2
As a side note, the tests are failing for me both with and without this change.