docker
Disk Image location movement
Tell us about your request
When you select Settings->Resources-Advanced and change the location of the current WSL data, a single message of "this might take long time" is shown in the screen after Apply & Restart is clicked, after a little while, everything looks like the process ended, when its not.
A progress bar, or at least "process hasnt finished yet" label could be usefull to track the movement.
Which service(s) is this request for? Docker.Desktop
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Not knowing when the transaction will end, and allowing to move around docker settings lead to a lost of time
Are you currently working around the issue? A single message is not enought to make sure completion of the task is visible
Additional context
This is my current screen. The process is not finished as i can tell by the Network Usage.
I can hit Cancel, close Docker, reboot computer, and i will have 2, 256GB data files, lingering, because i would never know how is this movement going.
Once y tried to delete the end file while it was being copied, and something like robocopy was doing its job. That was the hint that told me that the transaction was still ongoing...
Additional info, after 1 hour, the file was transfered, but at restart Docker, it broke the software somehow:
deploying WSL2 distributions ensuring main distro is deployed: deploying "docker-desktop": importing WSL distro "{Error de aplicación} Se produjo la excepción %s (0x\r\nCódigo de error: Wsl/Service/ERROR_UNHANDLED_EXCEPTION\r\n" output="docker-desktop": exit code: 4294967295: running WSL command wsl.exe C:\WINDOWS\System32\wsl.exe --import docker-desktop Y:\Docker\DockerDesktopWSL\main C:\Program Files\Docker\Docker\resources\wsl\wsl-bootstrap.tar --version 2: {Error de aplicación} Se produjo la excepción %s (0x Código de error: Wsl/Service/ERROR_UNHANDLED_EXCEPTION : exit status 0xffffffff checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache: The network name cannot be found.
Diagnostics: 17FD98A2-318B-4EF8-AA5D-B1C850514904/20250411175435
Thank you for reporting this! We are currently investigating. Meanwhile, can I confirm with you the following:
- Approximately how large was your Docker data that needed to be transferred?
- Did you have any containers running when you initiated the data location change?
- Have you successfully moved your WSL data location in previous Docker Desktop versions?
- Were you able to restore Docker Desktop functionality after the transfer failed? If so, what steps did you take?
- Were you using any custom WSL configurations (e.g. custom WSL kernel)?
Thank you for reporting this! We are currently investigating. Meanwhile, can I confirm with you the following:
- Approximately how large was your Docker data that needed to be transferred?
- Did you have any containers running when you initiated the data location change?
- Have you successfully moved your WSL data location in previous Docker Desktop versions?
- Were you able to restore Docker Desktop functionality after the transfer failed? If so, what steps did you take?
- Were you using any custom WSL configurations (e.g. custom WSL kernel)?
- 256GB
- Yes
- Didnt try other versions
- Reinstalled docker
- No