Disc image location - Does not persist Win 11pro, WSL2

[dzsoundnirvana]

• [x ] I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• [x ] I have uploaded Diagnostics
• Diagnostics ID: E60D0622-19F7-44F7-BA38-677DF7FCE795/20230312233546

Actual behavior

"Disc image location" in the "Resources" tab does not persist. Once Docker Desktop is closed the value is reset to default C:\Users<User>\AppData\Local\Docker\wsl
Additionally, when a path is provided such as "K:\Docker\ImageDir" the path is changed to "K:\Docker\ImageDir\DockerDesktopWSL"; "DockerDesktopWSL" is always appended. When observing this process in the %appdata%\Roaming\Docker\settings.json, the file will change on save but revert after the the "Apply & restart" has completed. This is also true once Docker Desktop has been closed and reopened.

Expected behavior

Persist provided Disc image location and do not append text to any given path

Information

• Windows Version: 11pro
• Docker Desktop Version: 4.17.0
• WSL2 or Hyper-V backend? WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: None, bare metal

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

[2023-03-13T00:03:05.929128700Z][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?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] 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?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [ 5.637957] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[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?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] 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?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? [ 5.637957] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[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] DD0032: do Docker networks overlap with host IPs?

Please note the following 1 warning:

1 : The check: is the WSL 2 Linux filesystem corrupt?
Produced the following warning: [ 5.637957] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal

If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
microsoft/WSL#5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.

Please investigate the following 1 issue:

1 : The test: is the WSL 2 Linux filesystem corrupt?
Failed with: [ 5.637957] EXT4-fs error (device sdc): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal

If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
microsoft/WSL#5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.

Note: Docker Desktop runs

Steps to reproduce the behavior

1. Open DD
2. Click settings in the upper left of the UI
3. Click Resources and click "Browse", find an existing path and select it
4. Click Apply & Restart
5. Observe the UI and the %appdata%\Roaming\Docker\settings.json; incorrect data

[pebezo]

Noticed the same issue in W10 with WSL1. I downgraded to Docker Desktop 4.16.3 and it worked

[mmarinchenko]

I have the same issue. The following workaround should help: #13408 (comment)

[gh-orange]

I have the same issue. The following workaround should help: #13408 (comment)

I have the same issue #13421. But the different thing is that I run on hyper-V!

[yzanhua]

A workaround that worked for me: issue comment