Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using SIGHUP to reload cluster configuration causes host and none networks to disappear until restart #1051

Closed
avuserow opened this issue Mar 25, 2016 · 1 comment

Comments

@avuserow
Copy link

On Docker 1.11 RC1, the host and none networks disappear when signaling the engine with SIGHUP after going from no configuration in /etc/docker/daemon.json to having cluster options (specifically, cluster-advertise, cluster-store, and cluster-store-opts). They reappear after a daemon restart.

@aboch
Copy link
Contributor

aboch commented Mar 25, 2016

Fixed by #1049

@aboch aboch closed this as completed Mar 25, 2016
mavenugo added a commit to mavenugo/docker that referenced this issue Mar 31, 2016
- Fixes moby/libnetwork#1051
- Fixes moby/libnetwork#985
- Fixes moby/libnetwork#945
- Log time taken to set sandbox key
- Limit number of concurrent DNS queries

Signed-off-by: Madhu Venugopal <madhu@docker.com>
tiborvass pushed a commit to tiborvass/docker that referenced this issue Mar 31, 2016
- Fixes moby/libnetwork#1051
- Fixes moby/libnetwork#985
- Fixes moby/libnetwork#945
- Log time taken to set sandbox key
- Limit number of concurrent DNS queries

Signed-off-by: Madhu Venugopal <madhu@docker.com>
(cherry picked from commit 90bb530)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants