#weavenetwork

Hi, I'm having problems resolving some upstream names through weaveDNS

Weave's upstream is set to 127.0.0.1, where a dnsmasq server is running (that's on the host), but I can't resolve names from dnsmasq on the containers

names from weaveDNS and further upstream (google.com and such) resolve correctly

Any idea why I wouldn't be able to resolve local names? resolution on the host works fine.

I wrote a short blog post illustrating some of the new robustness features in Weave Net 1.5 https://www.weave.works/reboot-tolerance-weave-...

quick question... after upgrading to weave 1.5.0, i frequently get this: "Unable to claim: 192.99.10.112/16 is in the range 192.99.0.0/16, but the allocator is not initialized yet", in this case im debugging right now it's on a 2 host weave network, I have ansible tearing down weave, launching weave, and then trying to start creating containers... when it does occur, by the time i can be on the server and check, manually r

is there some way to wait until weave is up/stabilized?

"claim" means it's not about a new container.

this may well be a bug. Please file it.

except in some special circumstances, you shouldn't have to explicitly wait - weave will do the waiting for you.

ok, now that im running it all manually i can reproduce... and im seeing the new deprecation warning about --init-peer-count, now reading up on new docs about new peer initialization options... your docs are not clear on how --name should be used i dont think, since you have --name ::1 and ::1 in the seed list... do they need to match? im using ipv4 and weave isn't letting me use an ipv4 address for a name

infact i cant come up with any --name value that seems to work...

File an issue, please.

Those docs need work.

the examples give in the docs *do* work though.

thanks