Cannot connect to the Docker daemon at unix:///var/run/weave/weave.sock. Is the docker daemon running?
systemctl status docker shows active and runningdocker ps will give this error
cannot connect to the Docker daemon at unix:///var/run/weave/weave.sock. Is the docker daemon running?
docker scope weave
edited Nov 15 '18 at 7:38
lagom
3,132102038
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
add a comment |
systemctl status docker shows active and runningdocker ps will give this error
cannot connect to the Docker daemon at unix:///var/run/weave/weave.sock. Is the docker daemon running?
docker scope weave
edited Nov 15 '18 at 7:38
lagom
3,132102038
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
Could see server start withdocker version?
– lagom
Nov 15 '18 at 6:59
try using sudo?
– Siyu
Nov 15 '18 at 9:37
add a comment |
systemctl status docker shows active and runningdocker ps will give this error
cannot connect to the Docker daemon at unix:///var/run/weave/weave.sock. Is the docker daemon running?
docker scope weave
edited Nov 15 '18 at 7:38
lagom
3,132102038
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
systemctl status docker shows active and runningdocker ps will give this error
cannot connect to the Docker daemon at unix:///var/run/weave/weave.sock. Is the docker daemon running?
docker scope weave
docker scope weave
edited Nov 15 '18 at 7:38
lagom
3,132102038
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
edited Nov 15 '18 at 7:38
lagom
3,132102038
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
edited Nov 15 '18 at 7:38
lagom
3,132102038
edited Nov 15 '18 at 7:38
lagom
3,132102038
edited Nov 15 '18 at 7:38
lagom
3,132102038
3,132102038
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
asked Nov 15 '18 at 6:15
Ravi _SSRavi _SS
83111
83111
Could see server start withdocker version?
– lagom
Nov 15 '18 at 6:59
try using sudo?
– Siyu
Nov 15 '18 at 9:37
add a comment |
Could see server start withdocker version?
– lagom
Nov 15 '18 at 6:59
try using sudo?
– Siyu
Nov 15 '18 at 9:37
Could see server start with
docker version?– lagom
Nov 15 '18 at 6:59
Could see server start with
docker version?– lagom
Nov 15 '18 at 6:59
try using sudo?
– Siyu
Nov 15 '18 at 9:37
try using sudo?
– Siyu
Nov 15 '18 at 9:37
add a comment |
1 Answer
1
active
oldest
votes
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.
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53313471%2fcannot-connect-to-the-docker-daemon-at-unix-var-run-weave-weave-sock-is-the%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
add a comment |
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.
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
add a comment |
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.
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
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.
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
answered Nov 15 '18 at 11:33
Michael BridgenMichael Bridgen
311
311
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53313471%2fcannot-connect-to-the-docker-daemon-at-unix-var-run-weave-weave-sock-is-the%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could see server start with
docker version?– lagom
Nov 15 '18 at 6:59
try using sudo?
– Siyu
Nov 15 '18 at 9:37