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

Perform arp configuration for plugin-connected containers #2374

Merged
merged 2 commits into from
Jun 17, 2016

Conversation

bboreham
Copy link
Contributor

Fixes #1726, the last remaining part.

Note that we are only reacting to container start events, so not doing the arp stuff when a user docker network connects a container. See #1914

bboreham added 2 commits June 14, 2016 17:52
so we don't have to remember all the endpoint IDs, or load them up
after a restart.
@bboreham bboreham added this to the 1.6.0 milestone Jun 14, 2016
@bboreham
Copy link
Contributor Author

There is the usual race arising from Docker sending the start event before actually starting the process. But we have to receive the event and complete the DNS-add http call before the interface is in place to lose the race.

@awh awh self-assigned this Jun 16, 2016
@@ -1747,6 +1747,7 @@ launch_plugin_if_not_running() {
if ! PLUGIN_CONTAINER=$(docker run -d --name=$PLUGIN_CONTAINER_NAME \
$(docker_run_options) \
$RESTART_POLICY \
--pid=host \

This comment was marked as abuse.

This comment was marked as abuse.

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

Successfully merging this pull request may close these issues.

3 participants