weave launch-proxy sets wrong weave env on docker for mac

[paulbellamy]

weaveworks/weave » git log --oneline | head -n1
589b45d Merge branch '1.6'
weaveworks/weave » docker version
Client:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.12.0
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   8eab29e
 Built:        Thu Jul 28 21:15:28 2016
 OS/Arch:      linux/amd64
weaveworks/weave » docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

weaveworks/weave » weave launch-proxy
weave container is not present. Have you launched it?
db5c3eeeef7ea85eb70b2dc9f55c73203c6a999f21f29f05084bfddebb951366
weaveworks/weave » docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS               NAMES
db5c3eeeef7e        weaveworks/weaveexec:latest   "/home/weave/weavepro"   20 seconds ago      Up 4 seconds                            weaveproxy
weaveworks/weave » weave env
export DOCKER_HOST=unix:///var/run/weave/weave.sock ORIG_DOCKER_HOST=
weaveworks/weave » (eval $(weave env) ; docker ps)
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

[alexandrem]

+1 same bug here

[mgregoro]

+1 I'm seeing this as well. Docker 1.12.1 on macOS 10.12. Funny thing is even when I launch with a TCP socket instead ala -H tcp://127.0.0.1:12367 there's nothing listening there. lsof -i tcp:12367 shows nothing.

[FatherShawn]

Still present in Docker for Mac Version 1.13.1 (15353)

Client:
 Version:      1.13.1
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      1.13.1
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   092cba3
 Built:        Wed Feb  8 08:47:51 2017
 OS/Arch:      linux/amd64
 Experimental: true

weave script 1.9.0
weave router 1.9.0
weave proxy 1.9.0
weave plugin 1.9.0

on MacOS 10.12.3 (16D32)

Is there a workaround?

[brb]

@errordeveloper @lukemarsden do you have any workaround for this?

[lukemarsden]

not afaik. I don't normally run weave on d4m. maybe @errordeveloper does though?

[errordeveloper]

I am not sure how much can be done here, it's really a bit tricky. Best we could do is make proxy listen on a TCP port, but it would be a huge special case. It doesn't have to use TLS and it can be tunnelled to localhost on the Mac.

[errordeveloper]

@brb happy to explain offline.

[FatherShawn]

OK thanks for the reply. My question was prompted by trying to replicate the steup in this WeaveWorks blog post, so maybe that should come down: https://www.weave.works/debugging-docker-mac-weave-net/ Good luck with the product!

[rade]

To be clear, does this issue only affect weave launch-proxy or also weave launch?

[errordeveloper]

It affects configuring docker client to use the proxy, so to me it mostly affects weave env. Proxy is socket is still functional inside the VM, it's just that it doesn't get exposed to macOS.

[mlabardini]

+1 any workarounds?

[corydodt]

It's been almost a year, any update here? Trying weave for the first time today, stuck because I don't know what env I actually need because weave env is doing something incorrect.