Docker-compose up : Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(61, 'Connection refused'))

Question

I am trying to do the docker-compose up command in my terminal. First I navigate to the file directory where I find a docker-compose.yaml. Then I write the command. The Server is on Port 80. I get the following error:

Traceback (most recent call last):
      File "site-packages/docker/api/client.py", line 205, in _retrieve_server_version
      File "site-packages/docker/api/daemon.py", line 181, in version
      File "site-packages/docker/utils/decorators.py", line 46, in inner
      File "site-packages/docker/api/client.py", line 228, in _get
      File "site-packages/requests/sessions.py", line 543, in get
      File "site-packages/requests/sessions.py", line 530, in request
      File "site-packages/requests/sessions.py", line 643, in send
      File "site-packages/requests/adapters.py", line 498, in send
    requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionRefusedError(61, 'Connection refused'))
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "docker-compose", line 3, in <module>
      File "compose/cli/main.py", line 67, in main
      File "compose/cli/main.py", line 123, in perform_command
      File "compose/cli/command.py", line 69, in project_from_options
      File "compose/cli/command.py", line 132, in get_project
      File "compose/cli/docker_client.py", line 43, in get_client
      File "compose/cli/docker_client.py", line 170, in docker_client
      File "site-packages/docker/api/client.py", line 188, in __init__
      File "site-packages/docker/api/client.py", line 213, in _retrieve_server_version
    docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(61, 'Connection refused'))
    [12728] Failed to execute script docker-compose

The first error shows up two times then the second.

Do you have the `$DOCKER_HOST` environment variable set? Is the Docker Desktop application running? — David Maze, Nov 03 '20 at 12:08
I tried: fiona@Fionas-MacBook-Pro gruppe-13 % docker run -d -p 80:80 docker/getting-started b35edd4bbab8ec87a0ef2beb793c4bb3382d5b878949bddca096ca1374bd84e9 docker: Error response from daemon: driver failed programming external connectivity on endpoint modest_agnesi (097923b153f0c23cb738591b39fff9c90479e4026add561cc847124d71b8b888): Bind for 0.0.0.0:80 failed: port is already allocated. Do you have an idea? — blackSwan566, Nov 03 '20 at 13:54

Zstack · Answer 1 · 2021-04-21T21:07:25.260

214

Add your user to docker group and try again.

sudo gpasswd -a $USER docker
newgrp docker

If you still have the problem, you may try after logging out and login back, or reboot. Or simply do:

sudo su $USER

Note: this may also happens if docker is not running on your machine. For linux with sytemd service manager, you could verify using command:

systemctl status docker.service

edited Apr 21 '21 at 21:07

answered Dec 10 '20 at 18:18

Zstack

4,046
1
19
22

2

What worked for me: resetting the docker, navigate to my projectfolder and do docker-compose up again. – blackSwan566 Jan 09 '21 at 11:58
Why in this order? I would have thought you would at first need to make a new group "docker" and then add the user to that group. If you check it with the command `groups` after the `sudo gpasswd -a $USER docker`, there is still no such group as "docker", it gets made by the `newgrp docker` in the end. Still works. Seems to map the user as the member of the group at first and matches that group name afterwards with any new group. – questionto42 Jul 29 '22 at 23:15

slideWXY · Answer 2 · 2022-02-17T12:34:37.713

71

just open Docker Desktop on your computer

edited Feb 17 '22 at 12:34

answered Mar 06 '21 at 14:04

slideWXY

1,121
8
9

18

Not a solution for cloud-based systems – Victor Marcelino Aug 17 '21 at 23:27
16

Does not work on ubuntu Linux – Noob Feb 22 '22 at 04:23
1

This actually worked for me on MacOS Catalina. – nydame Aug 03 '22 at 16:17
I don't know why but it worked for me on ubuntu 22.04 – Yulaow Nov 28 '22 at 00:41
@Noob btw docker desktop does exist on ubuntu linux – joel Jan 25 '23 at 12:05
This worked for me on Ubuntu 22.04 while no other option worked – Faizan Ahmad May 18 '23 at 04:58
well the docker desktop does exist. but don't use it if you have used something else. it does strange things to environment, creates new docker env. actually it is the cause of why I look at this question. – Galvani May 26 '23 at 08:16

score 56 · Answer 3 · answered Nov 17 '21 at 11:05

56

sudo chmod 666 /var/run/docker.sock

This worked for me

answered Nov 17 '21 at 11:05

Abdulhakim

655
6
9

5

This is **extremely** unsafe. FYI, giving a user access to docker.sock is like giving them sudo – Mouradif Nov 17 '21 at 11:17
1

"extremely unsafe" and whatever, but works. – Máxima Alekz Feb 08 '22 at 19:49
Obviously this, is not meant to be in a production server or something like that, just for testing/local purposes. – Máxima Alekz Feb 08 '22 at 19:50

score 14 · Answer 4 · answered Dec 19 '20 at 17:22

14

I had the same issue and error message. In my case i had to start and enable docker service.

systemctl start docker
systemctl enable docker

answered Dec 19 '20 at 17:22

koolwithk

685
8
14

5

`systemctl is-enabled docker` should show if docker is disabled or not – wi2ard Aug 19 '21 at 12:37

score 11 · Answer 5 · answered Mar 14 '21 at 01:55

11

Make sure your docker is actually running on your machine. You can use this post: How to check if the docker engine and a docker container are running?

answered Mar 14 '21 at 01:55

bisamov

650
1
8
24

Promise Preston · Answer 6 · 2022-07-27T17:33:27.240

9

To add clarity to Zstack's answer.

I encountered this issue while trying to setup Ansible AWX on Ubuntu 20.04

fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error connecting: Error while fetching server API version: ('Connection aborted.', PermissionError(13, 'Permission denied'))"} ...ignoring

Here's how I fixed it:

The issue was caused because I had not added my current user to the docker group.

Create the docker group if it does not already exist.

sudo groupadd docker

Add your user to the docker group.

sudo usermod -aG docker $USER

Log out and log back in so that your group membership is re-evaluated.

Verify that you can run docker commands without sudo.

docker ps

That's all.

edited Jul 27 '22 at 17:33

answered Aug 23 '21 at 18:01

Promise Preston

24,334
12
145
143

1

Doesn't work for me. – Eugene Gr. Philippov Nov 15 '21 at 21:58
1

I did not need the first command `sudo groupadd docker`, I guess that docker group is there by default. Then I ran `sudo usermod -aG docker myuser` (your code with `$USER` is better) and `sg docker -c "bash" ` and it worked. I am not sure whether the latter command was needed, someone can comment if so. – questionto42 Jul 27 '22 at 16:32

score 7 · Answer 7 · edited Dec 06 '21 at 09:47

7

Solution: This means you haven’t started your docker service!

First, try to start it using

１．sudo systemctl start docker

２．sudo service docker start

３．sudo /etc/init.d/docker restart

For More Info see this docs:here

edited Dec 06 '21 at 09:47

AthulMuralidhar

662
1
9
26

answered Dec 05 '21 at 14:25

cng.buff

405
4
5

`service docker start` worked in `wsl`, also can restart docker desktop / service in OS – Jason Jul 13 '22 at 18:46

score 2 · Answer 8 · answered Jan 06 '21 at 10:58

2

I had the same error after system and Docker updates on macOS Big Sur 11.1. I was also unable to run Docker Desktop, so I've checked the option open at login and simply restarted the system.

answered Jan 06 '21 at 10:58

mpro

14,302
5
28
43

For those having issue on MacOS, this solution works for me - https://leighmcculloch.com/posts/docker-context-via-ssh-with-macos/ – kctang Nov 01 '21 at 15:19

Murad Shukurlu · Answer 9 · 2022-02-02T06:53:16.370

This problem occurs due to docker user has no right access ,

After giving the right permissions and reconnecting to the server should solve the issue,

You can create the docker user if not exist

sudo groupadd docker

Add docker user to user group

usermod -aG docker $USER

Then reconnect to the server, it should work.

For more information this link is usefull : https://docs.docker.com/engine/install/linux-postinstall/

score 2 · Answer 10 · answered Mar 02 '22 at 05:08

2

I tried almost all the solutions above but for some reason what worked for me was sourcing the bashrc file:

source ~/.bashrc.

After this the error went away.

answered Mar 02 '22 at 05:08

anosha_rehan

1,522
10
17

thanks! works for me. I also tried almost solutions above.... but none of them worked. – hsuanyi-chou Jun 27 '22 at 08:54

score 1 · Answer 11 · answered May 24 '23 at 19:52

The error happend to me in production and linux machines, specially with amazon ec2 instances.

As a simple and safe solution:

First (of course, if using linux machines and systemd):

sudo systemctl enable docker.service
sudo systemctl start docker.service
sudo usermod -aG docker <here-your-user>

Make sure you logout and login again. Then, give executable permissions to docker compose binary:

sudo chmod +x /usr/local/bin/docker-compose

Try again!

score 0 · Answer 12 · answered Mar 16 '23 at 13:51

0

I've just encountered this problem on my Mac after upgrading to 4.17.0. I solved the problem by downgrading again to 4.16.2 from https://docs.docker.com/desktop/release-notes/.

answered Mar 16 '23 at 13:51

Alexander Pacha

9,187
3
68
108

score 0 · Answer 13 · answered May 25 '23 at 07:00

0

you can give docker socket read and write permission for other users by executing this command in your machine

sudo chmod o+rw /var/run/docker.sock

answered May 25 '23 at 07:00

Mohammed Ashraf

110
1
6

score 0 · Answer 14 · answered Jul 06 '23 at 07:45

0

For who is using WSL, make sure the WSL settings enabled, and restart Docker Desktop

answered Jul 06 '23 at 07:45

Yitong Feng

243
3
9

Docker-compose up : Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(61, 'Connection refused'))

14 Answers14

Linked