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

weave launch failed if weave expose was not undo with weave hide #1249

Closed
baopx opened this issue Jul 30, 2015 · 1 comment
Closed

weave launch failed if weave expose was not undo with weave hide #1249

baopx opened this issue Jul 30, 2015 · 1 comment

Comments

@baopx
Copy link

baopx commented Jul 30, 2015

This could be a work-flow issue rather a real bug... The following scenario will cause weave launch to fail.

weave launch && weave expose && weave stop
weave launch

network 10.128.0.0/10 would overlap with route 10.128.0.0/10
Default -iprange 10.128.0.0/10 overlaps with existing route.
Please pick another range and set it on all hosts.

In my case, I stopped docker without stopping weave. Then, my rerun of weave launch failed. To work around, I did:

ip link set weave down
brctl delbr weave

When we weave stop, should we hide exposed weave bridge?

Bao

@rade
Copy link
Member

rade commented Jul 31, 2015

dup of #1076

@rade rade closed this as completed Jul 31, 2015
@rade rade added the bug label Jul 31, 2015
@rade rade added this to the 1.1.0 milestone Jul 31, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants