-
Looks like docker 1.10.2 is not supported yet.
```
$ weave launch
level=fatal msg="Error response from daemon: 400 Bad Request: malformed Host header"
ERROR: Unable to determine docker version
```
…
-
Hello! Now I'm in troubles trying to run my application in a cluster environment using docker containers. I have a docker image with my application and a tomcat server. My application uses ehcache wit…
-
I've rolled out weave with Mesos, Marathon and Docker, and am seeing a concerning amount of netstat entries in netstat
```
unix 3 [ ] STREAM CONNECTED 6041473 /run/docker/plugi…
-
Given that:
- mobile devices are becoming more and more powerful,
- the most known issues with NIO and SSLEngine in ADK were fixed since Ice Cream Sandwich, and
- users obviously want to reuse their c…
-
Hi there,
Im using latest version of weave on docker 1.9.1 and i cant connect 2 nodes (p by the regular way
with weave launch .
im open the ports in both servers p01 and p02
firewall-cmd --zone=publ…
-
Requirements for taking that bounty:
- Expertise with Java
- Expertise with Tor
- Expertise with BitcoinJ
- Expertise with the usage of JTorProxy and the related libraries/network module in Bitsquare …
-
```
> docker -H unix:///var/run/docker.sock exec weaveproxy ls / > /dev/null
> docker -H unix:///var/run/weave/weave.sock exec weaveproxy ls / > /dev/null
unexpected EOF
```
-
I just upgraded to latest weave release v1.1.0. I'm running weave on ubuntu 15.04 server.
I launched weave using weave launch command. Here is the weave status
```
Version: v1.1.0
S…
-
Originally reported on Google Code with ID 190
```
I'd like to be able to completely purge the list of peers and supply a new PeerDiscovery.
All peers not discovered by the new discovery should be di…
-
```
I'd like to be able to completely purge the list of peers and supply a new
PeerDiscovery. All peers not discovered by the new discovery should be
disconnected.
Currently, I need to tear down Pe…