The location of the socket indicates that your $DOCKER_HOST environment variable has been set to point at the weave proxy. The fact that it doesn't respond means that the weave proxy is not running.
There are two remedies:
You can clear the environment variable, so that you're talking directly to docker again. Try
weave env --restore
or if that doesn't appear to work,
export DOCKER_HOST=
Or, you can try to get the weave proxy to run, so that it's there to answer on the socket. Try the link above for instructions.
The location of the socket indicates that your $DOCKER_HOST environment variable has been set to point at the weave proxy. The fact that it doesn't respond means that the weave proxy is not running.
There are two remedies:
weave env --restore
or if that doesn't appear to work,
export DOCKER_HOST=