docker
Unable to update, download update button does nothing
- [ ] I have tried with the latest version of Docker Desktop
- [x] I have tried disabling enabled experimental features
- [x] I have uploaded Diagnostics
- Diagnostics ID: D00688AA-249A-40CD-AD32-08E3D1F91109/20230414140401
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
- Windows Version: Windows 10 22h2
- Docker Desktop Version: 4.16.3
- WSL2 or Hyper-V backend? WSL2
- Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
"C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
[2023-04-14T14:07:40.811822200Z][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?
[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?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[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?
[WARN] DD0032: do Docker networks overlap with host IPs? network website_docker-php has subnet 172.23.0.0/16 which overlaps with host IP 172.23.48.1
Please note the following 1 warning:
1 : The check: do Docker networks overlap with host IPs?
Produced the following warning: network website_docker-php has subnet 172.23.0.0/16 which overlaps with host IP 172.23.48.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
No fatal errors detected.
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 2
Here 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.
Having the same issue. Cannot update from 4.18.0 (104112) to 4.19.0 (106363).
Text shows as "You're currently on version 4.18.0 (104112). The latest version is ()." before I click Update and restart
Only after clicking Update and restart does the text change to "You're currently on version 4.18.0 (104112). The latest version is 4.19.0 (106363).".
Update and restart button changes to a greyed out Installing update... and nothing happens.
Update worked fine on another machine.
Same issue here with Windows 11. "You're currently on version 4.18.0 (104112). The latest version is 4.19.0 (106363)." The "Installing Update" button is greyed out, but nothing happens.
Manually uninstalling 4.18 and installing 4.19 works without problems.
Same issue here with Windows 11. "You're currently on version 4.18.0 (104112). The latest version is 4.19.0 (106363)." The "Installing Update" button is greyed out, but nothing happens.
Manually uninstalling 4.18 and installing 4.19 works without problems.
This is what I did too
I have experiensed the same issue with Windows 11.
I could upgrade from 4.18 to 4.19 without uninstalling, by the following commands.
wsl -t "docker-desktop"
wsl -t "docker-desktop-data"
winget upgrade --id:"Docker.DockerDesktop"
Note: I could not even quit Docker Desktop from system tray icon. So, I tried to quit by terminating the WSL distributions which relate to Docker Desktop.
FWIW, I had the same problem trying to upgrade (on Windows 11) from DD 4.17.1 to 4.21 (the "update" button in the UI would do nothing, though I've done many updates in the past. It's just been a few months since the last. And restarting DD did not help, nor did shutting down WSL, nor did rebooting).
I found this thread and the above steps from @ecormaksin:
> wsl -t "docker-desktop"
> wsl -t "docker-desktop-data"
> winget upgrade --id:"Docker.DockerDesktop"
But for any who may prefer to use the Windows CMD prompt vs powershell, I had to change them just slightly:
> wsl -t docker-desktop
> wsl -t docker-desktop-data
> winget upgrade "Docker Desktop"
After it ran (not even needing to be "run as admin"), the update in the CLI finished, and the DD UI opened (itself prompting elevate as admin). It sat there "starting" for several mins longer than normal (I was a bit worried), but then it opened with the UI showing it was now indeed running on 4.21.
Thanks, @ecormaksin! :-)
