Failure to install and run Docker in WSL Ubuntu 22.04 (works in 20.04): "Cannot connect to the Docker daemon" #1406

40rn05lyv · 2022-06-09T17:46:02Z

This is a bug report
This is a feature request
I searched existing issues before opening this one

Steps to reproduce the behavior

OS: Windows 10 21H2

Enabled features: Virtual Machine Platform, Windows Subsystem for Linux

Steps:
Install a WSL Ubuntu 22.04 distribution and run it.
Set any username/password during installation password.
Perform all steps from official Docker installation guide (https://docs.docker.com/engine/install/ubuntu/):

sudo apt-get update
sudo apt-get install ca-certificates curl gnupg lsb-release
sudo mkdir -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin

Start service: sudo service docker start.

Verify installation: sudo docker run hello-world.

Expected behavior

sudo docker run hello-world starts a sample container.

Actual behavior

sudo docker run hello-world fails with a message docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?..

!!!!!!
NOTE: the same steps works ok with Ubuntu 20.04
!!!!!!

Output of docker version:

Docker version 20.10.17, build 100c701

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.8.2-docker)
  compose: Docker Compose (Docker Inc., v2.6.0)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
ERROR: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/info": dial unix /var/run/docker.sock: connect: permission denied
errors pretty printing info

The text was updated successfully, but these errors were encountered:

40rn05lyv · 2022-06-09T17:51:16Z

sudo journalctl -fu docker.service

gives

No journal files were found.

divyabhushan · 2022-06-10T15:05:21Z

Facing the same issue. Does anybody has a solution for this please?

WombleWoo7547 · 2022-06-14T15:17:07Z

Are you fully updated?
sudo apt update && sudo apt full-upgrade -y

If you are then maybe you could try using one of the 2 other ways :

curl -fsSL https://get.docker.com | sh
sudo apt update && sudo apt install docker.io -y

You could also try manually download the repo packages through wget on https://download.docker.com/linux/ubuntu/dists/jammy/pool/stable/amd64/
to get the packages for 22.04

phillip-haydon · 2022-06-17T06:39:55Z

Fully updated, services don't start at all. 22.04 is completely boinked.

sudo service ssh start
 * Starting OpenBSD Secure Shell server sshd
sshd: no hostkeys available -- exiting.

Adverte · 2022-06-23T13:45:07Z

It seems that you are using WSL version 1.
check the WSL version in Powershell
wsl -l -v
If you have version 1, WSL 1 did not support running Docker within the Ubuntu subsystem on its own. The WSL 1 required to use Windows Desktop Docker app to be installed and use windows binaries to run Docker within WSL. This is great if you need to keep the 2 docker services in sync.

If you want to run Docker within WSL without having the windows Docker client, you have to update it to WSL2.
Uninstall the current Ubuntu installation from Settings -> Apps -> Ubuntu.
Then switch the WSL version 2, then install the Ubuntu again.

divyabhushan · 2022-06-24T07:09:00Z

As a workaround in dev environment, I installed Docker using the convenience script that installed the latest stable release of Docker (Docker version 20.10.17, build 100c701) on my Ubuntu 20.04.4 LTS (Focal Fossa) machine.

40rn05lyv · 2022-06-24T08:53:39Z

@Adverte No, it's WSL 2.

ThaiLe011094 · 2022-07-13T17:23:46Z

In Ubuntu 22.04, it might have an issue with the iptables version. When checking the status, it might still show up not running. Hence, please make sure to switch the iptables to legacy.

To switch to iptables-legacy, run the below command to change the default iptables version.
sudo update-alternatives --config iptables

Then re-start docker service
sudo service docker start

And check docker status again with
sudo service docker status

If this can solve your problem, please close the issue.

YoshikoJanai · 2022-07-13T20:06:03Z

The above solution worked for me, without needing Docker Desktop.

I have no idea how modifying the iptables will affect everything else though.

Does this mean that we shouldn't bother with 22.04 for WSL in general and just stick with 20.04?

ThaiLe011094 · 2022-07-14T03:52:30Z

@YoshikoJanai imo, you can do anything you want, unless you want to have a specific feature that the lower version doesn't satisfy your desire.

ThaiLe011094 · 2022-07-14T03:54:54Z

@40rn05lyv did it work from your side?

spicysomtam · 2022-08-14T13:28:23Z

I had this issue with Linux Mint 21 upgrade; setting iptables to legacy fixed docker not starting.

pr13260 · 2022-08-16T19:10:36Z

similar issues for me too

tried some workarounds
and found that somehow if you keep sudo dockerd running in background it seems to be working normally
and then if you kill background task then whole thing turns back off

root@PRAKASH:~# nohup sudo dockerd &
[1] 2720
nohup: ignoring input and appending output to 'nohup.out'

root@PRAKASH:~# sudo docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:7d246653d0511db2a6b2e0436cfd0e52ac8c066000264b3ce63331ac66dca625
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

The Docker client contacted the Docker daemon.
The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/

For more examples and ideas, visit:
https://docs.docker.com/get-started/

root@PRAKASH:# ps -a
PID TTY TIME CMD
2720 pts/0 00:00:00 sudo
2722 pts/1 00:00:01 dockerd
2967 pts/0 00:00:00 ps
root@PRAKASH:# kill 2722
root@PRAKASH:# ps -a
PID TTY TIME CMD
2968 pts/0 00:00:00 ps
[1]+ Done nohup sudo dockerd
root@PRAKASH:# sudo docker run hello-world
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.

savagesmc · 2022-08-30T04:10:38Z

I had the same issue upon upgrading wsl to jammy 22.04. I changed iptables to legacy via update-alternatives like you suggested, and the docker service seems to be running now. Thank you.

vitorhingel · 2022-09-30T14:45:16Z

Was facing the same issue and solved with @ThaiLe011094 solution! Thank you!

oillypump · 2022-10-25T05:47:27Z

thanks it help, after upgrade to 22.04

JaragonCR · 2022-11-09T15:13:33Z

+1 on the firewall issue! thanks @ThaiLe011094

ylvall · 2022-11-14T19:43:00Z

Thank you.

D-Mabu · 2022-12-07T15:05:39Z

I had the same error; upgrading the Linux distro to WSL version 2 and integrating it to the Docker Windows fixed it.

https://docs.docker.com/desktop/windows/wsl/#enabling-docker-support-in-wsl-2-distros

michael-logan · 2023-02-03T22:22:53Z

elcreek · 2023-03-09T20:48:56Z

thanks

Jim-Fan · 2023-03-24T10:45:25Z

I was having same problem with Windows 11 Pro. Problem resolved after following @ThaiLe011094 's method.

Below is my machine configuration. Hope that helps.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:        22.04
Codename:       jammy
$ sudo docker version
Client: Docker Engine - Community
 Version:           23.0.1
 API version:       1.42
 Go version:        go1.19.5
 Git commit:        a5ee5b1
 Built:             Thu Feb  9 19:47:01 2023
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          23.0.1
  API version:      1.42 (minimum version 1.12)
  Go version:       go1.19.5
  Git commit:       bc3805a
  Built:            Thu Feb  9 19:47:01 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.19
  GitCommit:        1e1ea6e986c6c86565bc33d52e34b81b3e2bc71f
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Maxistor · 2023-04-01T21:51:52Z

After few hours of digging, your solution worked.
Thank you

7thWardMadeMe · 2023-04-17T05:06:52Z

Thanks! This worked for me! => sudo apt update && sudo apt full-upgrade -y

Peroconino · 2023-06-10T13:36:26Z

I have a similar problem but its a little bit different, i have installed docker desktop with wsl2 on my ubuntu 22.04. It worked pretty well the installation but when i try to run the hello-world container it keeps sending me this message:

docker: request returned Internal Server Error for API route and version http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create, check if the server supports the requested API version.

I wonder if there's anything i have done wrong...

EDIT: I have tried to switch the iptables to legacy but it didnt work.

aldington-david · 2023-07-20T09:01:01Z

same problems

kuhytitusdlz · 2023-07-20T12:03:28Z

after install it's work, but after reboot Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

AASanticioli · 2023-08-15T10:36:33Z

I have the same problem (Windows 11 + WSL 2 → Ubuntu 22.04.3 LTS).

I need to take some actions every morning (when I turn on my pc):

sudo dockerd --debug

That can't start and show me the message:

sudo rm -rf /var/run/docker.pid

sudo kill 25

sudo dockerd --debug
That starts normally. So I cancel it (CTRL+C)

sudo service docker start

That starts normallly.

After this, my day starts.

jonm01 · 2023-08-28T19:45:17Z

I have the same issue with WSL2 Ubuntu-22.04 on windows 11

failed to start daemon: Error initializing network controller: error obtaining controller instance: unable to add return rule in DOCKER-ISOLATION-STAGE-1 chain: (iptables failed: iptables --wait -A DOCKER-ISOLATION-STAGE-1 -j RETURN: iptables v1.8.7 (nf_tables): RULE_APPEND failed (No such file or directory): rule in chain DOCKER-ISOLATION-STAGE-1 (exit status 4))

switching iptables to legacy version solved the issue ( sudo update-alternatives --config iptables )

roadapathy · 2023-09-08T04:51:11Z

I get this error:
DEBU[2023-09-07T23:48:42.589375188-05:00] Cleaning up old mountid : done.
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.5.0-joeln2
iptables v1.8.7 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
(exit status 3)

I can tell right away this is due to my customized Kernel. Docker appears to need modules within the Kernel that most things don't need. I know that I stripped down IPtables. It would be nice to find a Docker list of Kernel module dependencies.

So for some of you, maybe try one of the default Ubuntu Kernels? I'll mess with this more this weekend, hopefully.

taovc · 2023-10-17T08:02:48Z

thanks , sudo apt update && sudo apt install docker.io -y that's working

devopsvas · 2023-10-30T17:00:18Z

This is the right solution, Thanks for posting the same.

victoranolu · 2023-11-18T01:26:44Z

This is the hack guys

ondapc · 2024-03-06T09:30:03Z

The issue I had was that apparently docker now installs via snap and well that causes a bit of a break -- where

sudo service docker start

returns a no docker.service file located

changed into directory: /etc/systemd/system/

I see a few snap.doccker files and decied to do a copy of

cp snap.docker.dockerd.service docker.service

Reboot machine or sudo systemctl daemon-reload

After that the command docker.service works as expected

odanilog4 · 2024-06-04T20:42:57Z

THIS REALLY WORKS.

but i reinstalled docker and follow these steps

40rn05lyv changed the title ~~"Cannot connect to the Docker daemon" on WSL Ubuntu 22.04 (works in 20.04)~~ Failure to install and run Docker in WSL Ubuntu 22.04 (works in 20.04): "Cannot connect to the Docker daemon" Jun 9, 2022

omichels mentioned this issue Jan 26, 2023

Cannot access registry.docker.io from worker nodes on WSL2 Debian 11 kubernetes-sigs/kind#2645

Closed

juliancervos mentioned this issue Jul 19, 2023

Ubuntu 22.04.2 LTS always Starting the Docker Engine Cannot connect to the Docker daemon at unix:///var/run/docker.sock docker/cli#4367

Closed

Chris2301 mentioned this issue Aug 9, 2023

WSL2 -> Ubuntu -> K3S cannot pull images after changing network k3s-io/k3s#8162

Closed

Failure to install and run Docker in WSL Ubuntu 22.04 (works in 20.04): "Cannot connect to the Docker daemon" #1406

Failure to install and run Docker in WSL Ubuntu 22.04 (works in 20.04): "Cannot connect to the Docker daemon" #1406

Comments

40rn05lyv commented Jun 9, 2022 • edited Loading

Steps to reproduce the behavior

Expected behavior

Actual behavior

40rn05lyv commented Jun 9, 2022

divyabhushan commented Jun 10, 2022

WombleWoo7547 commented Jun 14, 2022 • edited Loading

phillip-haydon commented Jun 17, 2022

Adverte commented Jun 23, 2022

divyabhushan commented Jun 24, 2022

40rn05lyv commented Jun 24, 2022

ThaiLe011094 commented Jul 13, 2022

YoshikoJanai commented Jul 13, 2022

ThaiLe011094 commented Jul 14, 2022

ThaiLe011094 commented Jul 14, 2022

spicysomtam commented Aug 14, 2022

pr13260 commented Aug 16, 2022 • edited Loading

savagesmc commented Aug 30, 2022

vitorhingel commented Sep 30, 2022

oillypump commented Oct 25, 2022

JaragonCR commented Nov 9, 2022

ylvall commented Nov 14, 2022

D-Mabu commented Dec 7, 2022

michael-logan commented Feb 3, 2023

elcreek commented Mar 9, 2023

Jim-Fan commented Mar 24, 2023

Maxistor commented Apr 1, 2023

7thWardMadeMe commented Apr 17, 2023

Peroconino commented Jun 10, 2023 • edited Loading

aldington-david commented Jul 20, 2023

kuhytitusdlz commented Jul 20, 2023

AASanticioli commented Aug 15, 2023

jonm01 commented Aug 28, 2023

roadapathy commented Sep 8, 2023 • edited Loading

taovc commented Oct 17, 2023

devopsvas commented Oct 30, 2023

victoranolu commented Nov 18, 2023

ondapc commented Mar 6, 2024 • edited Loading

odanilog4 commented Jun 4, 2024

40rn05lyv commented Jun 9, 2022 •

edited

Loading

WombleWoo7547 commented Jun 14, 2022 •

edited

Loading

pr13260 commented Aug 16, 2022 •

edited

Loading

Peroconino commented Jun 10, 2023 •

edited

Loading

roadapathy commented Sep 8, 2023 •

edited

Loading

ondapc commented Mar 6, 2024 •

edited

Loading