-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot Update Docker Desktop #6920
Comments
I am seeing the exact same problem on Mac amd64 when trying to update from v4.20.1 to latest. On Mac Apple Silicon (aarch64/arm64) the update worked correctly. |
Same problem here (same version - v4.20.1) on a MacBook Pro and on a Mac mini (both M1)... |
Same problem on macOS 12.6.6 (Intel chip), v4.20.1. |
Yes , It is Still Continue . * |
I uninstalled Docker Desktop and reinstalled it, let's see if this issue still happens - the version I downloaded and reinstalled is v4.21.1. |
Hello, thanks for the report. |
Updated from 4.21.1 to 4.22.0 via this UI; am now experiencing this issue on 4.22.0 Mind you, at the time of writing 4.22.0 is the latest version according to https://docs.docker.com/desktop/release-notes/, so it is possible it is the pending update notification that is incorrect here |
@rossjrw I have the same issue. Can't update to v4.22.1 (from v4.22.0)... |
@sergiuwaxmann can you share a diagnostics id? |
@bsousaa Sure: |
Can't update to v.4.22.1 from v.4.20.1 (macOS 13.5.1, Apple M1). |
@NBNGaming can you share a diagnostics id? |
@bsousaa |
I am having the same issue. I have had to manually upgrade Docker using |
I'm seeing the same thing, on macOS 13.5.1, trying to update from 4.22.0 to 4.22.1. Updating via |
Hello, Apologies for this! We currently have fixed the issue in 4.23.0, but this will most likely fix the issue for updates above 4.23. For now I suggest you use I'll close this issue for now, but if a problem persists above 4.23.0, feel free to open a new ticket. |
Version 4.24.0 have the same problem. It says it downloaded the update and asked me to restart. Restarting via the menu and manually doesn't actually upgrade the app. Macbook pro intel ventura |
@lorenrh Same thing in 4.25.0. |
Still having this issue. I can't go from 4.23.0 (120376) to 4.25.2 (129061). |
I was having the same issue.. stuck on 4.24.0 and updates would not apply. For me, the issue is that 4.25.x and up requires macOS 12 and I'm still on 11.7.x. The desktop app should not show updates available when the updates cannot be applied due to OS limitations. |
Finally used kill -9 on the demon docker processes and was able to uninstall, and then install the latest version. |
running 4.26.1 and update is still not working |
Hello @lmtyler can you send a diagnostic please? |
I think I possibly stumbled across the issue. I initially installed Docker Desktop via brew, then manually did an update via the download install. They were two different versions. Once I uninstalled the docker cask, which uninstalled everything done via brew, and then installed the dmg. The update button started working |
Oh! Nice! We are not testing interactions with brew, it is not Docker that maintains it so... |
Same problem on v4.23.0 on Mac Ventura arm64. |
Same problem on v4.31.0 on Mac Sonoma 14.6.1 arm64. |
The update functionality have not been working for long time. The only way to update is to remove the old docker manually and install again from fresh. Just tried the update with: After installing the update it still runs the old 4.34.0 (165256). Tried so many times updating between different versions and restarting after it and still stays at old. This happens at least with macOS Sonoma 14.6.1 on Intel chip. I suspect one of the cause is that if the Docker Desktop is installed on a non-administrator user account and during the update it does not ask for administrator credentials so it does not have all the permissions. For example when installing from the fresh it nicely asks for the admin credentials: Many other apps detect they don't have the admin permissions and ask the user to give the admin credentials and their update work fine. Some companies have policies and regulations that require users to run daily operations on separate non-admin accounts. EDIT: |
Cannot update on Mac Sonoma 14.6.1 Apple M2 Pro |
Also can not update Sonoma 14.7.1 Apple M1 Chip |
Cannot update Macbook Air M2 chip 15.1 Beta Sequoia |
Cannot update on Macbook Pro M2 Pro 14.7.1 |
Docker Desktop 4.37.0 has just been released, and it contains a fix for this issue! see: https://docs.docker.com/desktop/release-notes/ if the problem persists, feel free to open a new issue! |
Docker Desktop 4.37.0 solved the problem for me |
Same here. stuck in I solved it by uninstalling docker desktop and installing the new version of the release. afterwards update button works from Docker desktop 4.36.1 now I'm using 4.37.1 |
Still an issue for me. It always fails to update (seems to download the new version, shuts down the current one and then nothing happens). Also running as non admin account. This is annoying. |
Description
Hello,
After clicking download update in Docker Desktop, the install update button/dialog is missing.
Quitting & restarting the desktop app or my MacBook Pro did not help.
Reproduce
Expected behavior
The button/action to apply the update is available.
docker version
Client: Cloud integration: v1.0.33 Version: 24.0.2 API version: 1.43 Go version: go1.20.4 Git commit: cb74dfc Built: Thu May 25 21:51:16 2023 OS/Arch: darwin/amd64 Context: desktop-linux Server: Docker Desktop 4.20.1 (110738) Engine: Version: 24.0.2-38-g8e70a1b23e API version: 1.43 (minimum version 1.12) Go version: go1.20.4 Git commit: 8e70a1b23e965d86ec8c2feb77605196ae124630 Built: Fri Jun 2 15:58:50 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
9A0C7893-3C7D-4179-B6AD-C44BA32130B0/20230714181742
Additional Info
No response
The text was updated successfully, but these errors were encountered: