An unexpected error occurred.Restart Docker Desktop #13518

Jarvis-230529 · 2023-05-31T10:03:15Z

I have tried with the latest version of Docker Desktop
I have tried disabling enabled experimental features
I have uploaded Diagnostics
Diagnostics ID: 32C98272-B909-4E89-9FCD-C1CE70DF3C12/20230531093658

Actual behavior

Docker Desktop does not start and run as expected

Expected behavior

Docker Destop should start without any errors

Information

Windows Version: Windows11 Home 21H2
Docker Desktop Version: 4.20.0 (109717)
WSL2 or Hyper-V backend? WSL2
Are you running inside a virtualized Windows e.g. on a cloud server or a VM:No

Output of `& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check`

[2023-05-31T07:33:22.672349100Z][com.docker.backend.exe][I] (060f8b5c) e9dd27c6-BackendAPI S<-C Docker-Desktop/4.20.0 (Windows; x64) GET /ping [2023-05-31T07:33:22.672860100Z][com.docker.backend.exe][I] (060f8b5c) e9dd27c6-BackendAPI S->C Docker-Desktop/4.20.0 (Windows; x64) GET /ping (511碌s): {"serverTime":1685518402672860200} [2023-05-31T07:33:22.688060400Z][com.docker.backend.exe][E] getting WSL version: executing wsl --version: exit status 0xffffffff [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [common/pkg/eci.isValidWSLVersion() [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [ common/pkg/eci/eci_windows.go:55 +0x1f6 [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [common/pkg/eci.isSupportedOnHost(0x0?) [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [ common/pkg/eci/eci_windows.go:154 +0x1b [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [common/pkg/eci.IsSupportedOnHost(...) [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [ common/pkg/eci/eci.go:5 [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [common/cmd/com.docker.backend/internal/app.getGroupedSettings(_, {{0x0, 0x0}, {0x0, 0x0}, {{0x0, 0x0}, 0x0}, {{0x0, 0x0}, ...}, ...}, ...) [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [ common/cmd/com.docker.backend/internal/app/settings.go:250 +0x1c5 [2023-05-31T07:33:22.691488800Z][GoBackendProcess][I] [common/cmd/com.docker.backend/internal/app.ConvertToGroupedSettings(_) [2023-05-31T07:33:22.692020100Z][GoBackendProcess][I] [ common/cmd/com.docker.backend/internal/app/settings.go:207 +0x185 [2023-05-31T07:33:22.692020100Z][GoBackendProcess][I] [common/cmd/com.docker.backend/internal/app.GetSettings() [2023-05-31T07:33:22.692020100Z][GoBackendProcess][I] [ common/cmd/com.docker.backend/internal/app/settings.go:33 +0xf8 [2023-05-31T07:33:22.692020100Z][GoBackendProcess][I] [common/cmd/com.docker.backend/internal/handlers.(*AppHandler).GetSettings(0x0?, {0x2a0f278, 0xc0009a6750}) [2023-05-31T07:33:22.692020100Z][GoBackendProcess][I] [ common/cmd/com.docker.backend/internal/handlers/app.go:110 +0x78 [2023-05-31T07:33:22.692020100Z][GoBackendProcess][I] [github.com/labstack/echo/v4.(*Echo).add.func1({0x2a14cb8, 0xc0002ec500}) [2023-05-31T07:33:22.692020100Z][GoBackendProcess][I] [ github.com/labstack/echo/v4@v4.10.2/echo.go:575 +0x51 [2023-05-31T07:33:22.692414600Z][GoBackendProcess][I] [github.com/labstack/echo/v4/middleware.RecoverWithConfig.func1.1({0x2a14cb8, 0xc0002ec500}) [2023-05-31T07:33:22.692414600Z][GoBackendProcess][I] [ github.com/labstack/echo/v4@v4.10.2/middleware/recover.go:119 +0xfe [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [github.com/labstack/echo/v4.(*Echo).ServeHTTP(0xc00059ab40, {0x29f1bf0?, 0xc0000e81c0}, 0xc000c2ed00) [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [ github.com/labstack/echo/v4@v4.10.2/echo.go:662 +0x3d1 [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [net/http.serverHandler.ServeHTTP({0xc000629950?}, {0x29f1bf0, 0xc0000e81c0}, 0xc000c2ed00) [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [ net/http/server.go:2936 +0x316 [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [net/http.(*conn).serve(0xc000e12e10, {0x29f2980, 0xc0009a0150}) [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [ net/http/server.go:1995 +0x612 [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [created by net/http.(*Server).Serve [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [ net/http/server.go:3089 +0x5ed [2023-05-31T07:33:22.691488800Z][com.docker.backend.exe][W] (f80f6302) e9dd27c6-BackendAPI S->C Docker-Desktop/4.20.0 (Windows; x64) GET /app/settings (127.8155ms): determining canUseEnhancedContainerIsolation: executing wsl --version: exit status 0xffffffff [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [common/cmd/com.docker.backend/internal/handlers/app.go:112 github.com/docker/pinata/common/cmd/com.docker.backend/internal/handlers.(*AppHandler).GetSettings() [2023-05-31T07:33:22.692507500Z][GoBackendProcess][I] [common/pkg/ipc/server.go:230 github.com/docker/pinata/common/pkg/ipc.(*server).wrapHandlerFunc.func1() [2023-05-31T07:33:22.692917000Z][GoBackendProcess][I] [github.com/labstack/echo/v4@v4.10.2/echo.go:575 github.com/labstack/echo/v4.(*Echo).add.func1() [2023-05-31T07:33:22.692917000Z][GoBackendProcess][I] [github.com/labstack/echo/v4@v4.10.2/middleware/recover.go:119 github.com/labstack/echo/v4/middleware.RecoverWithConfig.func1.1() [2023-05-31T07:33:22.692917000Z][GoBackendProcess][I] [github.com/labstack/echo/v4@v4.10.2/echo.go:662 github.com/labstack/echo/v4.(*Echo).ServeHTTP() [2023-05-31T07:33:22.692917000Z][GoBackendProcess][I] [net/http/server.go:2936 net/http.serverHandler.ServeHTTP() [2023-05-31T07:33:22.692917000Z][GoBackendProcess][I] [net/http/server.go:1995 net/http.(*conn).serve() [2023-05-31T07:33:22.692917000Z][GoBackendProcess][I] [runtime/asm_amd64.s:1598 runtime.goexit()

Steps to reproduce the behavior

...
...

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

ctalledo · 2023-05-31T19:18:49Z

Hi @Jarvis-230529, sorry you hit a problem and thanks for filing the issue.

Could you provide the output of wsl --version on your Windows host (i.e., type that command on a Windows command prompt or powershell).

If the command fails it may mean you have an old version of WSL. Try updating it with wsl --update and then try wsl --version again. If that works, then try restarting Docker Desktop.

Thanks!

GTVolk · 2023-05-31T23:13:24Z

Having same issue, installed 4.20.0 over 4.18.0 today. Have "An unexpected error occured. Restart docker desktop".
Docker functionality works, console utils too, but settings in Docker Desktop not loading at all

Operating System: Windows 11 Pro (22H2) 22621.1778
Docker Desktop Version now is: 4.20.0 (109717) WSL2 backend
Not running in virtualized environment

wsl --update does not fixed problem, wsl --version output:

WSL version: 1.2.5.0
Core version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1778

com.docker.diagnose.exe check output one FAIL:
[FAIL] DD0014: are the backend processes running? 1 error occurred:
* com.docker.vpnkit.exe is not running
AND
segment 2023/06/01 02:06:09 ERROR: sending request - Post "https://api.segment.io/v1/batch": dial tcp: lookup api.segment.io: getaddrinfow: The requested name is valid, but no data of the requested type was found.
segment 2023/06/01 02:06:09 ERROR: 1 messages dropped because they failed to be sent and the client was closed

Docker Desktop 4.19.0 have no issue!
For now i'am downgrading to 4.19.0 before issue will be fixed. For now Docker desktop broken at all :(

P.S.: Deleted C:\ProgramData\DockerDesktop, %APPDATA%\Docker, %LOCALAPPDATA%\Docker folders making clean install of Docker Desktop 4.20.0, error persists out of box, making impossible to change any settings

Jarvis-230529 · 2023-06-01T01:54:08Z

@ctalledo
WSL version: 1.2.5.0
Core version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22000.1936
I updated the version but it didn't work. @GTVolk was right, it worked with the old version on another device.

xushijie10086 · 2023-06-01T05:12:04Z

@ctalledo
WSL version: 1.2.5.0
Core version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1702
metoo！！！

dph5199278 · 2023-06-01T05:59:22Z

@ctalledo
me too.

WSL version: 1.2.5.0
Core version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1702

Operating System: Windows 11 Pro (22H2) 22621.1702
Docker Desktop Version now is: 4.20.0 (109717) WSL2 backend

com.docker.diagnose.exe check output

[2023-06-01T05:52:46.030642000Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[SKIP] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 1 error occurred:
        * com.docker.vpnkit.exe is not running


[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[SKIP] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[WARN] DD0032: do Docker networks overlap with host IPs? network postfix_default has subnet 172.25.0.0/16 which overlaps with host IP 172.25.240.1

Please note the following 1 warning:

1 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: network postfix_default has subnet 172.25.0.0/16 which overlaps with host IP 172.25.240.1

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address


Please investigate the following 1 issue:

1 : The test: are the backend processes running?
    Failed with: 1 error occurred:
        * com.docker.vpnkit.exe is not running



Not all of the backend processes are running.

KTXKIKI · 2023-06-01T10:02:51Z

me too....

KTXKIKI · 2023-06-01T10:05:17Z

dockerdesktop 4.20有问题 4.19好好的更新4.20就不行了就报vpn虚拟网络组件起不来

17635093322 · 2023-06-01T14:27:34Z

wsl --version
WSL 版本： 1.2.5.0
内核版本： 5.15.90.1
WSLg 版本： 1.0.51
MSRDC 版本： 1.2.3770
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22621.1702
wsl --update
正在检查更新。
已安装最新版本的适用于 Linux 的 Windows 子系统。
出现同样的问题：
重装系统，重新安装软件多次，无法解决。
docker的settings设置无法更新，无法开机启动。
原本的容器和宿主机无法通信，显示被拒绝。

KTXKIKI · 2023-06-01T14:36:30Z

用 4.19吧

17635093322 · 2023-06-01T16:01:30Z

他这个有没有说是电脑安装wsl 2能够正常使用4.20咧，试过吗哥

ctalledo · 2023-06-01T16:32:54Z

Hi all, thanks for reporting the problem and apologies for the issue.

Looking at the Docker Desktop logs that @Jarvis-230529 uploaded, it's clear the problem is caused by Docker Desktop failing to get the WSL version on the host:

[2023-05-31T09:33:16.907785500Z][com.docker.backend.exe][E] getting WSL version: executing wsl --version: exit status 0xffffffff

It's not clear to me why that command fails when Docker Desktop (DD) executes it, given that @Jarvis-230529 indicated that typing the same command on a Powershell or Command prompt works:

wsl --version
WSL version: 1.2.5.0
Core version: 5.15.90.1
...

Very strange, and probably a WSL issue, but we will need to work around it.

On my host for example, Docker Desktop can execute the wsl --version command without problem, so instead of reporting an error it reports:

[2023-06-01T03:12:14.924086300Z][com.docker.backend.exe][I] WSL version (1.2.5.0) meets ECI requirement (>= 1.1.3)

and DD works fine.

The reason this shows up more prominently in DD 4.20 is that in this version, whenever a user opens the DD settings menu, DD will check the WSL version and cache it. But since the WSL version check is failing, the problem causes DD to not work properly.

Will work on a fix/work-around ASAP.

ctalledo · 2023-06-01T16:47:16Z

FYI, most users of Docker Desktop on WSL don't hit this issue, but we are investigating why some do. For now, the only work-around for users that hit the problem is to stay on DD 4.19.

six1203 · 2023-06-01T16:59:54Z

FYI, most users of Docker Desktop on WSL don't hit this issue, but we are investigating why some do. For now, the only work-around for users that hit the problem is to stay on DD 4.19.

I also encountered this problem, wsl --version has output, this is the diagnosis id I uploaded
7B07B43E-C797-4B34-964E-E4D4F1D8898D/20230601165636

GTVolk · 2023-06-01T17:27:23Z

@ctalledo I think this is because of localized Windows interface package. In my case wsl --version gives me localized output, so here i've pasted translated to english version before.

If i am right, DD using regex expression without case of locale detection...

ctalledo · 2023-06-01T17:35:56Z

@ctalledo I think this is because of localized Windows interface package. In my case wsl --version gives me localized output, so here i've pasted translated to english version before.

If i am right, DD using regex expression without case of locale detection...

Thanks @GTVolk; could you provide the output of wsl --version without the translation please?

In this particular issue, the wsl --version command is failing with exit status 0xffffffff, so it's not clear to me it's a locale related issue (though it could be).

However in issue #13524, it's definitely a locale related bug: DD is adjusting for locale when parsing the output of wsl --version, but I think there is a bug in the regex that we did not catch unfortunately.

GTVolk · 2023-06-01T18:34:38Z

@ctalledo

Версия WSL: 1.2.5.0
Версия ядра: 5.15.90.1
Версия WSLg: 1.0.51
Версия MSRDC: 1.2.3770
Версия Direct3D: 1.608.2-61064218
Версия DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Версия Windows: 10.0.22621.1778

rc5hack · 2023-06-01T18:38:50Z

The same text output as in issue #13524, but with different "Windows version" minor number (10.0.22621.1702 in #13524 , but 10.0.22621.1778 here)

KTXKIKI · 2023-06-01T19:44:39Z

等官方修复吧 wsl2也一样所有方法我都试过 dockerdesktop windows用户目前唯一解决办法是用4.19

ctalledo · 2023-06-01T22:10:44Z

FYI we have a fix in progress, will be available in the next few days. Apologies again and thanks for your patience.

zhoujie0420 · 2023-06-02T01:02:25Z

mac 都用的好好的 win就挂我傻了

DouShaoxun · 2023-06-02T01:23:44Z

wsl --version

WSL 版本： 1.2.5.0
内核版本： 5.15.90.1
WSLg 版本： 1.0.51
MSRDC 版本： 1.2.3770
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22621.1778

wsl --update

正在检查更新。
已安装最新版本的适用于 Linux 的 Windows 子系统。

kingnight797 · 2023-06-02T08:57:25Z

如何下载老版本呀

KTXKIKI · 2023-06-02T09:27:34Z

https://docs.docker.com/desktop/release-notes/

如何下载老版本呀

jjcc123312 · 2023-06-03T08:04:43Z

me too

WSL 版本： 1.2.5.0
内核版本： 5.15.90.1
WSLg 版本： 1.0.51
MSRDC 版本： 1.2.3770
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22621.1778

FreshmanMa · 2023-06-03T14:33:57Z

me too
WSL 版本： 1.2.5.0
内核版本： 5.15.90.1
WSLg 版本： 1.0.51
MSRDC 版本： 1.2.3770
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22000.1936

karthest · 2023-06-03T16:51:18Z

WSL 版本： 1.2.5.0
内核版本： 5.15.90.1
WSLg 版本： 1.0.51
MSRDC 版本： 1.2.3770
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows 版本： 10.0.22621.1778

aziyoufei · 2023-06-04T16:11:37Z

我也是同样的问题，换回4.19.0版本就可以了

fcuneyt · 2023-06-04T18:51:34Z

different windows version same issue here.

WSL sürümü: 1.2.5.0
Çekirdek sürümü: 5.15.90.1
WSLg sürümü: 1.0.51
MSRDC sürümü: 1.2.3770
Direct3D sürümü: 1.608.2-61064218
DXCore sürümü: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows sürümü: 10.0.19045.3031

Hod0ri · 2023-06-05T02:45:58Z

When Docker Desktop is launched or when entering the options window,
the mentioned error notification appears at the top.
Is there any action I should take?
And most importantly, are there any issues with using Docker?
I keep seeing the message, but everything seems to be working fine.
For reference, my WSL version is as follows.
Thanks

WSL version: 1.2.5.0
Core version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1702

ctalledo · 2023-06-05T05:01:08Z

When Docker Desktop is launched or when entering the options window, the mentioned error notification appears at the top. Is there any action I should take? And most importantly, are there any issues with using Docker? I keep seeing the message, but everything seems to be working fine.

Hi @Hod0ri, this is a bug in Docker Desktop's 4.20 parsing of the WSL version in some locales, and it only affects the options window display. It does not affect Docker CLI commands from working properly. The issue will be resolved very soon. Apologies for the inconvenience.

lorenrh · 2023-06-05T16:47:46Z

We've release docker Desktop 4.20.1, containing a fix for this issue, so I'm closing this issue.

For more information, head to https://docs.docker.com/desktop/release-notes/.

paule96 · 2023-06-06T06:43:46Z

For me the fix is not working. I still get the issue above.

It runs for 5mins and then it shuts off.

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[SKIP] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 1 error occurred:
        * com.docker.vpnkit.exe is not running


[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[SKIP] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[WARN] DD0032: do Docker networks overlap with host IPs? network master_devcontainer_network has subnet 172.20.0.0/16 which overlaps with host IP 172.20.240.1

Please note the following 1 warning:

1 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: network master_devcontainer_network has subnet 172.20.0.0/16 which overlaps with host IP 172.20.240.1

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address


Please investigate the following 1 issue:

1 : The test: are the backend processes running?
    Failed with: 1 error occurred:
        * com.docker.vpnkit.exe is not running



Not all of the backend processes are running.

Note that DD0021 is also skipped, so it looks like the same issue here, that WSL2 can't be detected.

Environment:
WSL version: 1.2.5.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2965

ctalledo · 2023-06-07T04:35:41Z

Hi @paule96, thanks for reporting. It's unlikely to be the same exact issue, but we will help you debug it. Could you please upload a Docker Desktop diagnostic bundle? That will help us see what's going on.

paule96 · 2023-06-07T04:44:20Z

hm I can't reproduce it now. I guess a reboot of the whole system did helped.

docker-robott added the version/4.20.0 label May 31, 2023

lorenrh added the area/startup label May 31, 2023

bsousaa added the status/triage label Jun 1, 2023

ctalledo mentioned this issue Jun 1, 2023

win11 版本 21H2， docekr desktop 启动报错 An unexpected error occurred. Restart Docker Desktop. #13519

Closed

ctalledo mentioned this issue Jun 1, 2023

"unexpected error occurred" when starting Docker Desktop on Windows 11 Home #13524

Closed

bsousaa added status/acknowledged and removed status/triage labels Jun 2, 2023

lorenrh closed this as completed Jun 5, 2023

anton-filatov mentioned this issue Jan 9, 2024

Docker Desktop tries to update wsl each startup #13868

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

An unexpected error occurred.Restart Docker Desktop #13518

An unexpected error occurred.Restart Docker Desktop #13518

Jarvis-230529 commented May 31, 2023

ctalledo commented May 31, 2023 •

edited

GTVolk commented May 31, 2023 •

edited

Jarvis-230529 commented Jun 1, 2023

xushijie10086 commented Jun 1, 2023

dph5199278 commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023

17635093322 commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023

17635093322 commented Jun 1, 2023

ctalledo commented Jun 1, 2023

ctalledo commented Jun 1, 2023

six1203 commented Jun 1, 2023

GTVolk commented Jun 1, 2023

ctalledo commented Jun 1, 2023

GTVolk commented Jun 1, 2023

rc5hack commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023 •

edited

ctalledo commented Jun 1, 2023

zhoujie0420 commented Jun 2, 2023

DouShaoxun commented Jun 2, 2023

kingnight797 commented Jun 2, 2023

KTXKIKI commented Jun 2, 2023

jjcc123312 commented Jun 3, 2023

FreshmanMa commented Jun 3, 2023

karthest commented Jun 3, 2023

aziyoufei commented Jun 4, 2023

fcuneyt commented Jun 4, 2023

Hod0ri commented Jun 5, 2023

ctalledo commented Jun 5, 2023

lorenrh commented Jun 5, 2023

paule96 commented Jun 6, 2023

ctalledo commented Jun 7, 2023

paule96 commented Jun 7, 2023

An unexpected error occurred.Restart Docker Desktop #13518

An unexpected error occurred.Restart Docker Desktop #13518

Comments

Jarvis-230529 commented May 31, 2023

Actual behavior

Expected behavior

Information

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

Steps to reproduce the behavior

ctalledo commented May 31, 2023 • edited

GTVolk commented May 31, 2023 • edited

Jarvis-230529 commented Jun 1, 2023

xushijie10086 commented Jun 1, 2023

dph5199278 commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023

17635093322 commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023

17635093322 commented Jun 1, 2023

ctalledo commented Jun 1, 2023

ctalledo commented Jun 1, 2023

six1203 commented Jun 1, 2023

GTVolk commented Jun 1, 2023

ctalledo commented Jun 1, 2023

GTVolk commented Jun 1, 2023

rc5hack commented Jun 1, 2023

KTXKIKI commented Jun 1, 2023 • edited

ctalledo commented Jun 1, 2023

zhoujie0420 commented Jun 2, 2023

DouShaoxun commented Jun 2, 2023

wsl --version

wsl --update

kingnight797 commented Jun 2, 2023

KTXKIKI commented Jun 2, 2023

jjcc123312 commented Jun 3, 2023

FreshmanMa commented Jun 3, 2023

karthest commented Jun 3, 2023

aziyoufei commented Jun 4, 2023

fcuneyt commented Jun 4, 2023

Hod0ri commented Jun 5, 2023

ctalledo commented Jun 5, 2023

lorenrh commented Jun 5, 2023

paule96 commented Jun 6, 2023

ctalledo commented Jun 7, 2023

paule96 commented Jun 7, 2023

Output of `& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check`

ctalledo commented May 31, 2023 •

edited

GTVolk commented May 31, 2023 •

edited

KTXKIKI commented Jun 1, 2023 •

edited