Can't able to start Docker Engine in Docker Desktop

[jindalamit34567]

Description

deploying WSL2 distributions
ensuring data disk is available: exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --

Diagnostics ID--
7A124CA7-4D7A-4CF5-BF8C-763F7DD959C8/20250208074732

Reproduce

N/A

Expected behavior

No response

docker version

Docker version 27.5.1, build 9f9e405

docker info

No output

Diagnostics ID

7A124CA7-4D7A-4CF5-BF8C-763F7DD959C8/20250208074732

Additional Info

deploying WSL2 distributions
ensuring data disk is available: exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --

Diagnostics ID--
7A124CA7-4D7A-4CF5-BF8C-763F7DD959C8/20250208074732

[andreasgou]

Same here, trying to update to version 38.x

Recover WSL Distro does not fix the issue.
Diagnostics ID:
17C1812F-A830-4798-9E89-8786BA0EA1BB/20250210085543

Additional info:
deploying WSL2 distributions
ensuring data disk is available: resetting disk identifier: setting new UUID: setting virtual disk identifier: opening virtual disk: permission denied (1300) (is the vhdx open in another process?)
checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache: The filename, directory name, or volume label syntax is incorrect.

UPDATE: a reboot fixed the problem

[moroboro]

Confirm the same problem as described above
Diagnostics ID: 83021112-6103-48BC-A696-E5A354A4897D/20250212141056

UPDATE: Everything went back to normal after the reboot

[Georges-Crypto]

If i reboot my computer everything goes away??

[moroboro]

If i reboot my computer everything goes away??

At least on my side everything went back to the way it was before. Even the container selection...

[marcvanandel]

I do have the same issue ... it seems. I was running Ubuntu 22.04 in WSL and I had this error off and on. Error message:

Process doesn't have access to the file because it is in use by some other program.

Resetting my WSL environment and using the newer Ubuntu 24.04 it seemed resolved ... until some days later 😏

Error message details:

ensuring data disk is available: exit code: 4294967295: running WSL command wsl.exe C:\windows\System32\wsl.exe --mount --bare --vhd \AppData\Local\Docker\wsl\disk\docker_data.vhdx: Failed to attach disk '\?<HOME>\AppData\Local\Docker\wsl\disk\docker_data.vhdx' to WSL2: Het proces heeft geen toegang tot het bestand omdat het door een ander proces wordt gebruikt.

Workaround solution:

1. Open PowerShell (normal privilege level)
2. Mount by hand running the command: wsl.exe --mount --bare --vhd $HOME\AppData\Local\Docker\wsl\disk\docker_data.vhdx
3. Start Docker Desktop 💪

[Georges-Crypto]

No it's working for me, i had to unistall and install again WSL for the Docker Engine to start. Den tis 4 mars 2025 12:11Marc van Andel ***@***.***> skrev:

…

I do have the same issue ... it seems. I was running Ubuntu 22.04 in WSL and I had this error off and on. Error message: Process doesn't have access to the file because it is in use by some other program. Resetting my WSL environment and using the newer Ubuntu 24.04 it seemed resolved ... until some days later 😏 Error message details: ensuring data disk is available: exit code: 4294967295: running WSL command wsl.exe C:\windows\System32\wsl.exe --mount --bare --vhd \AppData\Local\Docker\wsl\disk\docker_data.vhdx: Failed to attach disk '\?<HOME>\AppData\Local\Docker\wsl\disk\docker_data.vhdx' to WSL2: Het proces heeft geen toegang tot het bestand omdat het door een ander proces wordt gebruikt. Workaround solution: 1. Open PowerShell (normal privilege level) 2. Mount by hand running the command: wsl.exe --mount --bare --vhd $HOME\AppData\Local\Docker\wsl\disk\docker_data.vhdx 3. Start Docker Desktop 💪 — Reply to this email directly, view it on GitHub <#14584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOZXOZQHM2VLJLPCKPUEWJ32SWC45AVCNFSM6AAAAABWXOAJIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJXGE2DAOJZHA> . You are receiving this because you commented.Message ID: ***@***.***> [image: marcvanandel]*marcvanandel* left a comment (docker/for-win#14584) <#14584 (comment)> I do have the same issue ... it seems. I was running Ubuntu 22.04 in WSL and I had this error off and on. Error message: Process doesn't have access to the file because it is in use by some other program. Resetting my WSL environment and using the newer Ubuntu 24.04 it seemed resolved ... until some days later 😏 Error message details: ensuring data disk is available: exit code: 4294967295: running WSL command wsl.exe C:\windows\System32\wsl.exe --mount --bare --vhd \AppData\Local\Docker\wsl\disk\docker_data.vhdx: Failed to attach disk '\?<HOME>\AppData\Local\Docker\wsl\disk\docker_data.vhdx' to WSL2: Het proces heeft geen toegang tot het bestand omdat het door een ander proces wordt gebruikt. Workaround solution: 1. Open PowerShell (normal privilege level) 2. Mount by hand running the command: wsl.exe --mount --bare --vhd $HOME\AppData\Local\Docker\wsl\disk\docker_data.vhdx 3. Start Docker Desktop 💪 — Reply to this email directly, view it on GitHub <#14584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOZXOZQHM2VLJLPCKPUEWJ32SWC45AVCNFSM6AAAAABWXOAJIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJXGE2DAOJZHA> . You are receiving this because you commented.Message ID: ***@***.***>

[marcvanandel]

Hm.. It seems that a restart also helps to release the lock ... sometimes. So is there somewhere a process that locks this file? 🤔 Could this be a process of the Docker Desktop? Or has it something to do with the WSL set up?

[jindalamit34567]

Thank you for your email, this is a process of Docker desktop only. Amit Jindal

…

On Thu, 13 Mar, 2025, 1:42 pm Marc van Andel, ***@***.***> wrote: Hm.. It seems that a restart also helps to release the lock ... sometimes. So is there somewhere a process that locks this file? 🤔 Could this be a process of the Docker Desktop? Or has it something to do with the WSL set up? — Reply to this email directly, view it on GitHub <#14584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNRJEXPKNXJDE3RYXGRWY6L2UE4WXAVCNFSM6AAAAABWXOAJIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRQGMZDEMRXGM> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: marcvanandel]*marcvanandel* left a comment (docker/for-win#14584) <#14584 (comment)> Hm.. It seems that a restart also helps to release the lock ... sometimes. So is there somewhere a process that locks this file? 🤔 Could this be a process of the Docker Desktop? Or has it something to do with the WSL set up? — Reply to this email directly, view it on GitHub <#14584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNRJEXPKNXJDE3RYXGRWY6L2UE4WXAVCNFSM6AAAAABWXOAJIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMRQGMZDEMRXGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[marcvanandel]

It seems my virus scanner is the issue here ... 😏