ERROR: Couldn't connect to Docker daemon at http+docker://localhost + Segmentation Fault on docker daemon
up vote
0
down vote
favorite
I installed docker at my raspberry pi zero w running the latest raspbian with
curl -sSL https://get.docker.com | sh
and docker-compose with
sudo pip install docker-compose
When I run docker-compose in my raspberry:
sudo docker-compose up
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
When I do sudo dockerd:
sudo dockerd
Segmentation fault
It seems that the docker daemon is not working because of the Segmentation Fault. What should I do?
services docker raspberrypi pip
asked Nov 10 at 13:32
Guerlando OCs
731214
add a comment |
up vote
0
down vote
favorite
I installed docker at my raspberry pi zero w running the latest raspbian with
curl -sSL https://get.docker.com | sh
and docker-compose with
sudo pip install docker-compose
When I run docker-compose in my raspberry:
sudo docker-compose up
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
When I do sudo dockerd:
sudo dockerd
Segmentation fault
It seems that the docker daemon is not working because of the Segmentation Fault. What should I do?
services docker raspberrypi pip
asked Nov 10 at 13:32
Guerlando OCs
731214
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I installed docker at my raspberry pi zero w running the latest raspbian with
curl -sSL https://get.docker.com | sh
and docker-compose with
sudo pip install docker-compose
When I run docker-compose in my raspberry:
sudo docker-compose up
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
When I do sudo dockerd:
sudo dockerd
Segmentation fault
It seems that the docker daemon is not working because of the Segmentation Fault. What should I do?
services docker raspberrypi pip
asked Nov 10 at 13:32
Guerlando OCs
731214
I installed docker at my raspberry pi zero w running the latest raspbian with
curl -sSL https://get.docker.com | sh
and docker-compose with
sudo pip install docker-compose
When I run docker-compose in my raspberry:
sudo docker-compose up
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
When I do sudo dockerd:
sudo dockerd
Segmentation fault
It seems that the docker daemon is not working because of the Segmentation Fault. What should I do?
services docker raspberrypi pip
services docker raspberrypi pip
asked Nov 10 at 13:32
Guerlando OCs
731214
asked Nov 10 at 13:32
Guerlando OCs
731214
asked Nov 10 at 13:32
Guerlando OCs
731214
asked Nov 10 at 13:32
Guerlando OCs
731214
asked Nov 10 at 13:32
Guerlando OCs
731214
731214
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Looks like there's a known issue with 18.09 and ARMv6 processors. Discussion and downgrade instructions here:
https://github.com/moby/moby/issues/38175
answered Nov 16 at 15:53
Snap E Tom
16
Hello and welcome to Ask Ubuntu! Link-only answers are discuraged here (what if the link goes dead or is moved somewhere else?). Please edit your answer and explain the step needed to resolve the issue.
– Mr Shunz
Nov 16 at 16:10
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Looks like there's a known issue with 18.09 and ARMv6 processors. Discussion and downgrade instructions here:
https://github.com/moby/moby/issues/38175
answered Nov 16 at 15:53
Snap E Tom
16
Hello and welcome to Ask Ubuntu! Link-only answers are discuraged here (what if the link goes dead or is moved somewhere else?). Please edit your answer and explain the step needed to resolve the issue.
– Mr Shunz
Nov 16 at 16:10
add a comment |
up vote
0
down vote
accepted
Looks like there's a known issue with 18.09 and ARMv6 processors. Discussion and downgrade instructions here:
https://github.com/moby/moby/issues/38175
answered Nov 16 at 15:53
Snap E Tom
16
Hello and welcome to Ask Ubuntu! Link-only answers are discuraged here (what if the link goes dead or is moved somewhere else?). Please edit your answer and explain the step needed to resolve the issue.
– Mr Shunz
Nov 16 at 16:10
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Looks like there's a known issue with 18.09 and ARMv6 processors. Discussion and downgrade instructions here:
https://github.com/moby/moby/issues/38175
answered Nov 16 at 15:53
Snap E Tom
16
Looks like there's a known issue with 18.09 and ARMv6 processors. Discussion and downgrade instructions here:
https://github.com/moby/moby/issues/38175
answered Nov 16 at 15:53
Snap E Tom
16
answered Nov 16 at 15:53
Snap E Tom
16
answered Nov 16 at 15:53
Snap E Tom
16
answered Nov 16 at 15:53
Snap E Tom
16
16
Hello and welcome to Ask Ubuntu! Link-only answers are discuraged here (what if the link goes dead or is moved somewhere else?). Please edit your answer and explain the step needed to resolve the issue.
– Mr Shunz
Nov 16 at 16:10
add a comment |
Hello and welcome to Ask Ubuntu! Link-only answers are discuraged here (what if the link goes dead or is moved somewhere else?). Please edit your answer and explain the step needed to resolve the issue.
– Mr Shunz
Nov 16 at 16:10
Hello and welcome to Ask Ubuntu! Link-only answers are discuraged here (what if the link goes dead or is moved somewhere else?). Please edit your answer and explain the step needed to resolve the issue.
– Mr Shunz
Nov 16 at 16:10
Hello and welcome to Ask Ubuntu! Link-only answers are discuraged here (what if the link goes dead or is moved somewhere else?). Please edit your answer and explain the step needed to resolve the issue.
– Mr Shunz
Nov 16 at 16:10
add a comment |
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%2faskubuntu.com%2fquestions%2f1091690%2ferror-couldnt-connect-to-docker-daemon-at-httpdocker-localhost-segmentati%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
