WSL 在Docker desktop的集成操作过程中，虚拟磁盘意外离线并导致会话中断

[lynchx]

Windows Version

Microsoft Windows [版本 10.0.26200.8246]

WSL Version

2.6.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04

Other Software

Docker Desktop(Windows),version 4.71.0

Repro Steps

1、在“任务计划程序”中将“wsl”命令作为启动时的命令。
2、开机后打开docker desktop，然后开启“Enable integration with my default WSL distro”选项，等待约5分钟就会出现报错

Expected Behavior

正常情况下，在开启了“Enable integration with my default WSL distro”选项后，即可在ubuntu中使用docker命令了

Actual Behavior

docker desktop报错显示wsl突然中断通信：

Diagnostic Logs

1、我通过docker的日志发现以下信息：
问题不是 Docker daemon 本身，而是 Docker Desktop 的 WSL 集成在对 Ubuntu 执行初始化命令时，Ubuntu 侧的代理会话先掉了。

最关键的链路是：

• Docker Desktop 先执行 com.docker.backend.exe.log
• 随后在给 Ubuntu 配置 docker 用户组时失败，返回 com.docker.backend.exe.log
• 后端紧接着报出 com.docker.backend.exe.log
• 早一点的同类失败还显示在获取家目录时，变成了 com.docker.backend.exe.log

这说明“pipe is being closed”是结果，不是根因。根因是 Ubuntu WSL 实例在 Docker Desktop 做 whoami/setup groups/echo $HOME 这类初始化动作时，WSL 服务端把连接断掉了，导致 Docker Desktop 认为 Ubuntu 的 distro agent 异常退出。

2、于是我接着去找wsl的日志，我通过dmesg捕获到了复现问题时遇到的报错：
2026-05-02T12:16:39,386529+08:00 br-c4ea83d8ef41: port 1(veth56ee6c3) entered disabled state
2026-05-02T12:16:39,386656+08:00 vethaa3ed11: renamed from eth0
2026-05-02T12:16:39,486445+08:00 br-c4ea83d8ef41: port 1(veth56ee6c3) entered disabled state
2026-05-02T12:16:39,488314+08:00 veth56ee6c3 (unregistering): left allmulticast mode
2026-05-02T12:16:39,488327+08:00 veth56ee6c3 (unregistering): left promiscuous mode
2026-05-02T12:16:39,488331+08:00 br-c4ea83d8ef41: port 1(veth56ee6c3) entered disabled state
2026-05-02T12:16:39,656383+08:00 br-c4ea83d8ef41: port 3(veth625d9ce) entered disabled state
2026-05-02T12:16:39,656569+08:00 veth95e9c8c: renamed from eth0
2026-05-02T12:16:39,714100+08:00 br-c4ea83d8ef41: port 3(veth625d9ce) entered disabled state
2026-05-02T12:16:39,715320+08:00 veth625d9ce (unregistering): left allmulticast mode
2026-05-02T12:16:39,715323+08:00 veth625d9ce (unregistering): left promiscuous mode
2026-05-02T12:16:39,715334+08:00 br-c4ea83d8ef41: port 3(veth625d9ce) entered disabled state
2026-05-02T12:16:39,960563+08:00 br-c4ea83d8ef41: port 2(veth3bc1921) entered disabled state
2026-05-02T12:16:39,960595+08:00 veth43f57b6: renamed from eth0
2026-05-02T12:16:40,040519+08:00 br-c4ea83d8ef41: port 4(veth03ab834) entered disabled state
2026-05-02T12:16:40,040711+08:00 veth28c60ef: renamed from eth0
2026-05-02T12:16:40,077451+08:00 br-c4ea83d8ef41: port 2(veth3bc1921) entered disabled state
2026-05-02T12:16:40,078778+08:00 veth3bc1921 (unregistering): left allmulticast mode
2026-05-02T12:16:40,078782+08:00 veth3bc1921 (unregistering): left promiscuous mode
2026-05-02T12:16:40,078792+08:00 br-c4ea83d8ef41: port 2(veth3bc1921) entered disabled state
2026-05-02T12:16:40,158191+08:00 br-c4ea83d8ef41: port 4(veth03ab834) entered disabled state
2026-05-02T12:16:40,159536+08:00 veth03ab834 (unregistering): left allmulticast mode
2026-05-02T12:16:40,159540+08:00 veth03ab834 (unregistering): left promiscuous mode
2026-05-02T12:16:40,159552+08:00 br-c4ea83d8ef41: port 4(veth03ab834) entered disabled state
2026-05-02T12:16:47,196339+08:00 Exception:
2026-05-02T12:16:47,196343+08:00 Operation canceled @p9io.cpp:258 (AcceptAsync)

2026-05-02T12:16:47,255368+08:00 device offline error, dev sde, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2
2026-05-02T12:16:47,265867+08:00 device offline error, dev sde, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2
2026-05-02T12:16:47,324072+08:00 EXT4-fs (sde): shut down requested (2)
2026-05-02T12:16:47,324491+08:00 Aborting journal on device sde-8.
2026-05-02T12:16:47,324791+08:00 device offline error, dev sde, sector 1073479680 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
2026-05-02T12:16:47,325338+08:00 device offline error, dev sde, sector 1073479680 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
2026-05-02T12:16:47,325892+08:00 Buffer I/O error on dev sde, logical block 134184960, lost sync page write
2026-05-02T12:16:47,326309+08:00 JBD2: I/O error when updating journal superblock for sde-8.
2026-05-02T12:16:47,393662+08:00 sd 0:0:0:5: [sde] Synchronizing SCSI cache
2026-05-02T12:16:47,575106+08:00 scsi 0:0:0:5: Direct-Access Msft Virtual Disk 1.0 PQ: 0 ANSI: 5
2026-05-02T12:16:47,579805+08:00 sd 0:0:0:5: Attached scsi generic sg5 type 0
2026-05-02T12:16:47,580035+08:00 sd 0:0:0:5: [sdf] 2147483648 512-byte logical blocks: (1.10 TB/1.00 TiB)
2026-05-02T12:16:47,580047+08:00 sd 0:0:0:5: [sdf] 4096-byte physical blocks
2026-05-02T12:16:47,580109+08:00 sd 0:0:0:5: [sdf] Write Protect is off
2026-05-02T12:16:47,580110+08:00 sd 0:0:0:5: [sdf] Mode Sense: 0f 00 00 00
2026-05-02T12:16:47,580202+08:00 sd 0:0:0:5: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
2026-05-02T12:16:47,581815+08:00 sd 0:0:0:5: [sdf] Attached SCSI disk
2026-05-02T12:16:47,754908+08:00 WSL (1 - init(docker-desktop)) ERROR: ConfigApplyWindowsLibPath:2092: open /etc/ld.so.conf.d/ld.wsl.conf failed 2
2026-05-02T12:16:47,791964+08:00 WSL (1 - init(docker-desktop)) WARNING: /usr/share/zoneinfo/Asia/Shanghai not found. Is the tzdata package installed?
2026-05-02T12:16:47,945469+08:00 EXT4-fs (sde): unmounting filesystem 5a191135-00d4-4a7c-9913-ab15a0d96049.
2026-05-02T12:16:47,978659+08:00 misc dxg: dxgk: dxgkio_is_feature_enabled: Ioctl failed: -22
2026-05-02T12:16:47,985416+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
2026-05-02T12:16:47,985962+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
2026-05-02T12:16:47,986434+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
2026-05-02T12:16:47,986915+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:47,995875+08:00 EXT4-fs (sdf): recovery complete
2026-05-02T12:16:47,997947+08:00 EXT4-fs (sdf): mounted filesystem 5a191135-00d4-4a7c-9913-ab15a0d96049 r/w with ordered data mode. Quota mode: none.
2026-05-02T12:16:48,026689+08:00 loop0: detected capacity change from 0 to 1672996
2026-05-02T12:16:48,026927+08:00 ISO 9660 Extensions: Microsoft Joliet Level 3
2026-05-02T12:16:48,027052+08:00 ISO 9660 Extensions: RRIP_1991A
2026-05-02T12:16:48,044010+08:00 loop1: detected capacity change from 0 to 1465880
2026-05-02T12:16:48,044381+08:00 ISO 9660 Extensions: RRIP_1991A
2026-05-02T12:16:48,053432+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,129826+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,130500+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,130959+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,131444+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,131890+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,132288+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,132717+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,133174+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,133589+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,134033+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,134672+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,135160+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,135620+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,136030+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,136422+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,136929+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,177892+08:00 misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
2026-05-02T12:16:48,268020+08:00 netlink: 'initd': attribute type 4 has an invalid length.
2026-05-02T12:16:48,705391+08:00 virtiofs: Unknown parameter 'negative_dentry_timeout'
2026-05-02T12:16:49,139466+08:00 WSL (15814 - SessionLeader) ERROR: UtilBindVsockAnyPort:320: bind failed 4
2026-05-02T12:16:49,140021+08:00 WSL (15814 - SessionLeader) ERROR: SessionLeaderEntryUtilityVm:3027: InitCreateProcessUtilityVm failed
2026-05-02T12:16:53,134514+08:00 br-c4ea83d8ef41: port 1(veth19e7888) entered blocking state
2026-05-02T12:16:53,134527+08:00 br-c4ea83d8ef41: port 1(veth19e7888) entered disabled state
2026-05-02T12:16:53,134535+08:00 veth19e7888: entered allmulticast mode
2026-05-02T12:16:53,134568+08:00 veth19e7888: entered promiscuous mode
2026-05-02T12:16:53,151937+08:00 br-c4ea83d8ef41: port 1(veth19e7888) entered blocking state
2026-05-02T12:16:53,151941+08:00 br-c4ea83d8ef41: port 1(veth19e7888) entered forwarding state
2026-05-02T12:16:53,151995+08:00 br-c4ea83d8ef41: port 1(veth19e7888) entered disabled state
2026-05-02T12:16:53,193662+08:00 br-c4ea83d8ef41: port 2(veth0b1bcfd) entered blocking state
2026-05-02T12:16:53,193666+08:00 br-c4ea83d8ef41: port 2(veth0b1bcfd) entered disabled state
2026-05-02T12:16:53,193671+08:00 veth0b1bcfd: entered allmulticast mode
2026-05-02T12:16:53,193695+08:00 veth0b1bcfd: entered promiscuous mode
2026-05-02T12:16:53,214325+08:00 br-c4ea83d8ef41: port 2(veth0b1bcfd) entered blocking state
2026-05-02T12:16:53,214330+08:00 br-c4ea83d8ef41: port 2(veth0b1bcfd) entered forwarding state
2026-05-02T12:16:53,214425+08:00 br-c4ea83d8ef41: port 2(veth0b1bcfd) entered disabled state
2026-05-02T12:16:53,235400+08:00 br-c4ea83d8ef41: port 3(veth1e17458) entered blocking state
2026-05-02T12:16:53,235403+08:00 br-c4ea83d8ef41: port 3(veth1e17458) entered disabled state
2026-05-02T12:16:53,235411+08:00 veth1e17458: entered allmulticast mode
2026-05-02T12:16:53,235433+08:00 veth1e17458: entered promiscuous mode
2026-05-02T12:16:53,266437+08:00 br-c4ea83d8ef41: port 3(veth1e17458) entered blocking state
2026-05-02T12:16:53,266439+08:00 br-c4ea83d8ef41: port 3(veth1e17458) entered forwarding state
2026-05-02T12:16:53,308251+08:00 br-c4ea83d8ef41: port 4(vethed2556b) entered blocking state
2026-05-02T12:16:53,308255+08:00 br-c4ea83d8ef41: port 4(vethed2556b) entered disabled state
2026-05-02T12:16:53,308262+08:00 vethed2556b: entered allmulticast mode
2026-05-02T12:16:53,308283+08:00 vethed2556b: entered promiscuous mode
2026-05-02T12:16:53,349642+08:00 br-c4ea83d8ef41: port 4(vethed2556b) entered blocking state
2026-05-02T12:16:53,349644+08:00 br-c4ea83d8ef41: port 4(vethed2556b) entered forwarding state
2026-05-02T12:16:53,573143+08:00 br-c4ea83d8ef41: port 3(veth1e17458) entered disabled state
2026-05-02T12:16:53,573165+08:00 br-c4ea83d8ef41: port 4(vethed2556b) entered disabled state
2026-05-02T12:16:54,067402+08:00 eth0: renamed from veth46b34f3
2026-05-02T12:16:54,086810+08:00 br-c4ea83d8ef41: port 1(veth19e7888) entered blocking state
2026-05-02T12:16:54,086813+08:00 br-c4ea83d8ef41: port 1(veth19e7888) entered forwarding state
2026-05-02T12:16:54,100035+08:00 eth0: renamed from vethac52732
2026-05-02T12:16:54,140239+08:00 br-c4ea83d8ef41: port 2(veth0b1bcfd) entered blocking state
2026-05-02T12:16:54,140264+08:00 br-c4ea83d8ef41: port 2(veth0b1bcfd) entered forwarding state
2026-05-02T12:16:54,157513+08:00 eth0: renamed from vethc4638ed
2026-05-02T12:16:54,201569+08:00 eth0: renamed from veth001f27b
2026-05-02T12:16:54,231290+08:00 br-c4ea83d8ef41: port 3(veth1e17458) entered blocking state
2026-05-02T12:16:54,231294+08:00 br-c4ea83d8ef41: port 3(veth1e17458) entered forwarding state
2026-05-02T12:16:54,231512+08:00 br-c4ea83d8ef41: port 4(vethed2556b) entered blocking state
2026-05-02T12:16:54,231515+08:00 br-c4ea83d8ef41: port 4(vethed2556b) entered forwarding state

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[lynchx]

WslLogs-2026-05-02_15-25-36.tar.gz
已上传wsl日志

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.6.3.0
Detected user visible error: Wsl/Service/0x8007274c

[chemwolf6922]

Hi @lynchx , this looks like the same issue as #14541. Where a bind call was interrupted by an unrelated signal. This issue was fixed in #14554. Could you please try update to the latest pre-release version (2.7.3) to see if the issue persists? Thanks.

[lynchx]

等到2.7.3稳定版推出后我更新到了最新版，发现这个问题已经解决了。非常感谢！