SudoCerb
commented
1 year ago Hi,
Please note I am experiencing the exact same behaviour when trying to update from 4.18.0 (104112) to 4.19.0 (106363). However I have some strange issues apparently... despite the errors you're about to see - I am currently running and using my Docker installation.
Relevant system specs: OS Name Microsoft Windows 11 Enterprise Version 10.0.22621 Build 22621 Processor Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz, 2112 Mhz, 4 Core(s), 8 Logical Processor(s) Installed Physical Memory (RAM) 32.0 GB
here's my output from wsl -l -v :
NAME STATE VERSION
* Debian Running 2
Ubuntu Stopped 2
docker-desktop-data Running 2
docker-desktop Running 2Here is my output from docker diagnose:
[2023-05-04T15:40:59.095891800Z][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?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[FAIL] DD0035: is the VM time synchronized? parsing time output: 2023-05-04T15:41:06+00:00: parsing time "2023-05-04T15:41:06+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
[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?
[FAIL] DD0005: is the user in the docker-users group? The user name could not be found.
[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?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[WARN] DD0035: is the VM time synchronized? parsing time output: 2023-05-04T15:41:06+00:00: parsing time "2023-05-04T15:41:06+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
[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 bridge has subnet 172.17.0.0/16 which overlaps with host IP 172.17.240.1
Please note the following 2 warnings:
1 : The check: is the VM time synchronized?
Produced the following warning: parsing time output: 2023-05-04T15:41:06+00:00: parsing time "2023-05-04T15:41:06+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.
Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists,
try manually synchronizing the VM clock with "sudo hwclock -s".
2 : The check: do Docker networks overlap with host IPs?
Produced the following warning: network bridge has subnet 172.17.0.0/16 which overlaps with host IP 172.17.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: is the VM time synchronized?
Failed with: parsing time output: 2023-05-04T15:41:06+00:00: parsing time "2023-05-04T15:41:06+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.
Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists,
try manually synchronizing the VM clock with "sudo hwclock -s".I have attempted to synchronize the VM clock using the suggested command sudo hwclock -s, but without success - this looks like a locale issue.
brainz80
Cito
ecormaksin
we684123
carehart
rbargerhuff
Actual behavior
Pressing the "Download Update" does nothing. I have also enabled "Always download updates" but it has no effect
Expected behavior
Update button should at least show error if something is not working.
Information
Output of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check