Unable to update from 3.3.1 to newer version

[flowl]

• [x] 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:

Docker Desktop for Mac 3.3.1 (63452) Engine 20.10.5 Compose 1.29.0

After hitting "Download update" and "Update and restart", the menu item to "Download update" and "Update and restart" still show up.

"Update and restart" doesn't do anything other than restart.

Tried several times in the past days, restarted my macbook,... no error message, the program is just restarting without any update.

[stusmall]

I'm hitting the same issue. Here is an interesting clue, on the Update screen the version is (). I am on 3.3.2 though

[deltamualpha]

Same behavior, no obvious failures reported. Manually exiting, then downloading and installing 3.3.3 from the website appears to have unstuck it, but who knows what the next update will bring.

[waleed-dawood]

same issue.

Update : Somehow quitting and restarting docker desktop helped. It was able to download and install the update after that.

I had tried "quitting and restarting" before. But perhaps you need to do it more than once for it to work.

[flowl]

Feature request: It would be nice if from the "Troubleshoot" modal there was an option to display the applications STDERR or logs.

[flowl]

After quitting and restarting, Docker Desktop upgraded to 3.3.2 instead of 3.3.3 or newer. Whole update thing is buggy.

[hepcat72]

Same issue. 3.3.1. I also constantly get a dialog a couple times a day and I always click download and update, but it just always comes back and the menu item always has the (!) badge. Or maybe the button is "install and restart".

[jeroenvanmaanen]

I had the same issue. I tried Update and Restart a few times with out effect. Then I Quit Docker Dektop and started it again, now I am on 3.3.3. 😅

[flowl]

The update from 3.3.3 to 3.4.0 seemed to work at first but ended in a seg fault after entering the credentials.

I clicked on "Upload Crash Report" but nothing happened. No confirmation, no insight, I don't know if the report got sent or not.

I expect the software to show me the report before sending so I can assert no personal or company related information is getting uploaded.

Not only is the update process bugged since 3.3, there is also a privacy issue now.

Edit: Despite the error, the update got installed and docker engine is starting with 3.4.0.

[StefanScherer]

Thanks @flowl for the report. We see more users to have this issue, but we're still investigating why this happens to some users. We couldn't reproduce it on our test machines yet. But we're looking into it.

[deltamualpha]

Having the same issue upgrading past 3.3.3 now as well. Are there any logs I can pull to help debugging, @StefanScherer?

[flowl]

The upgrade from 3.4.1 to 3.5.1 worked perfectly, no seg fault, no loops, no issues.

[craigotis]

I'm also seeing this on 3.5.0, with a 3.5.1 update available.

[deltamualpha]

It must have something to do with how Docker for Mac is installed. Or perhaps it's running into a conflict with something installed using homebrew? I know homebrew doesn't love that docker-for-mac installs its own kubectl...

[sgronblo]

My Docker was unable to restart itself with the new version. But after quitting and restarting I finally could go from 3.3.x to 3.5.2.

[BeatriceThalo]

I'm on Big Sur, started on 3.3.3, the "install and restart" button was on a loop, despite "Shut Down" my mac each night for a few weeks and the notification showing each morning. Today, "Quit Docker Desktop" and then relaunching Docker from Launchpad, prompted me with 'Docker will ask you for a password' and then 'Docker needs to install a helper tool' where I typed in my password (my usual fingerprint wasn't offered in the dialog). Then the notification changed to ask about the August 11th update, and About Docker Desktop shows 3.5.2.

[gennaro-tedesco]

I see the same problem, similar to what is being referenced here. Issues for Docker are being automatically locked and closed after some days without any solution or fix: is anyone looking into it at all? I find it somewhat puzzling that this still happens after so many opened tickets (buggy behaviour in the first place but let it be so).

[sean-hernon]

I see the same problem, similar to what is being referenced here. Issues for Docker are being automatically locked and closed after some days without any solution or fix: is anyone looking into it at all? I find it somewhat puzzling that this still happens after so many opened tickets (buggy behaviour in the first place but let it be so).

At least there is the option to skip updates and not be spammed with a pop-up periodically.

Oh wait...

[netmikey]

Here's another clue: I'm still on 10.15.7 Catalina and I had the same issue from Docker Desktop 3.5.2 to 3.6.0. Explicitly choosing "Quit docker desktop" and relaunching "docker.app" from the quick launch solved it for me too. When docker.app relaunched, I quickly saw macOS's Gatekeeper verifying some downloaded software (you know, just the small window with a security icon and a progress bar). And voila, docker started with v3.6.0.

[ssb22]

Same on macOS Big Sur 11.5.2 upgrading to Docker Desktop 3.6.0, was repeatedly prompted for Upgrade every time I logged in, and when accepting the upgrade I saw network traffic as it was downloading, only to be prompted again at next login (so it was re-downloading every day, adding unnecessary load to the servers). Like @netmikey the problem seems to have disappeared after Docker Desktop was explicitly quit and re-launched. Don't know if this information is useful at all.

[steezeburger]

13" Apple Silicon MBP, macOS Big Sur 11.5.2 upgrading to Docker Desktop 3.6.0 from 3.5.2.18:

I downloaded and installed Docker Desktop 4. Seemed to fix the issue for me.

[jwoertink]

Same here. I get a daily reminder to update, but no matter how many times I click the "Update and restart", it never updates. macOS 11.6 Intel.

[saludes]

Same here with the same settings of @jwoertink but on macOS 11.6 Apple M1

[lylepratt]

Same problem

[asmaier]

With brew I was able to workaround the issue doing

❯ brew upgrade --cask docker --greedy
==> Upgrading 1 outdated package:
docker 3.5.2,66501 -> 4.1.1,69879

The upgrade took a lot of time, so be patient. Afterwards I restarted the docker app and everything worked fine again.

[gennaro-tedesco]

It is unreal how bad this is, and nobody looking at it. Might as well just close the issue, it has been months.

[akkapur]

With brew I was able to workaround the issue doing

❯ brew upgrade --cask docker --greedy
==> Upgrading 1 outdated package:
docker 3.5.2,66501 -> 4.1.1,69879

The upgrade took a lot of time, so be patient. Afterwards I restarted the docker app and everything worked fine again.

Works on my machine!

[joeyfezster]

same issue, haven't tried tried the brew upgrade

[tapz]

I always need to download the installation package to update to a new version. Update and restart does nothing.

[ageron]

I had the same issue on MacOSX 10.15.7, where it kept asking me to update, and never did. I quit Docker Desktop, I waited for a minute, and when I restarted it, it asked me for admin rights (I had to type my password), and when it started it was updated to the latest version. 👍

So perhaps it's an authorization issue where we're not getting the security popup on MacOSX 10.15.7 or something like that? Hope this helps.

[sbleon]

Me too. This is pretty irritating, and it's my main complaint about Docker Desktop right now.

[StefanScherer]

We have a know sporadic issue with the update experience which started in 3.3.x version. For some users it always feels like the update does nothing.

It normally updates when you quit Docker Desktop and start it again.

If that still doesn‘t work we recommend to download the latest version of Docker Desktop from the release page https://docs.docker.com/desktop/mac/release-notes/

In newer versions we have fixed this update issue. Future updates will work as usual, but you need to update manually once to get it fixed. We apologize for any inconvenience.

[tapz]

I downloaded and installed 4.3.0 over 3.3.x and the 4.3.1 update is downloaded, but not installed when I select Install & Restart. I need to manually quit and start again Docker Desktop.

[flowl]

My experience in the last months / last updates is congruent to what @StefanScherer commented. I don't think any new or relevant information can be shared here unless the problem still exists with current versions (e.g. you want to update from 4.2 to 4.3 and it fails) which is not the case for me. I don't know about your internal tasks (says 1 of 3 tasks are done) but from my pov this issue can be closed. Thanks everyone who participated and thanks to the Docker Team for their great product and responsiveness during this issue.

[tapz]

@flowl How can this be closed when the Update and restart menu item clearly does not work?

[flowl]

@tapz Oh I think I misunderstood your comment, sorry! The update from 4.3.0 to 4.3.1 should work but if it doesn't, the problem still exists and the issue shouldn't get closed.

[tapz]

4.x works better than in 3.3.x as the update gets installed after quitting docker desktop. But the Update and restart menu item still does not cause the update to be installed.

[dhlavaty]

I have "Download will start soon..." message for a few days now. I restarted my Mac, restarted Docker, tried "Update and Restart", several times. Nothing helps.

Big Sur 11.6.2, Docker Desktop 4.1.1

[zhengyongtao]

In fact, the main reason for this phenomenon is that the restart and update option did not kill the com.docker.vmnetd process. After killing com.docker.vmnetd, the docker process can be updated normally by running it again.

[JoneSabino]

brew upgrade --cask docker --greedy

This worked fine. Hope they fix it in the product.

[rluncasu]

In fact, the main reason for this phenomenon is that the restart and update option did not kill the com.docker.vmnetd process. After killing com.docker.vmnetd, the docker process can be updated normally by running it again.

• killed com.docker.vmnetd
• clicked on update & restart
• manually closed docker
• started docker was updated

[tapz]

For me it's enough to just manually close Docker Desktop and start it again. No need to kill vmnetd. Just updated to 4.4.2 (73305).

[1298509345]

In fact, the main reason for this phenomenon is that the restart and update option did not kill the com.docker.vmnetd process. After killing com.docker.vmnetd, the docker process can be updated normally by running it again.

• killed com.docker.vmnetd
• clicked on update & restart
• manually closed docker
• started docker was updated

It's ok ,thanks

[flowl]

Updating from Version 4.4.2, state of the app is stuck between "Downloading update" and "Ready to apply update". After waiting for two days without any changes to that state, I restarted Docker and it already had upgraded to 4.5.0.

[flowl]

Version still buggy, download does not start:

You’re currently on version 4.5.0 (74594). The latest version is 4.6.1 (76265)

[ntvinhit]

Why does this issue still occurs for a year without a bug fix :(

[flowl]

I don't understand how people are able to create such a revolutionary, genius system like Docker, but at the same time can't fix a simple update process within a year. The update doesn't work even after restarting, there is always "Download will start soon..."

[tapz]

I haven't seen this issue since 4.6.0. Update and restart works perfectly fine in MacOS 12.

[flowl]

I am stuck with this, no matter how many times I restart my Macbook or Docker or Docker Desktop. MacOS 11.16.1

I think I'd have to reinstall but I need to work and can't waste time to try and fix Docker everytime it has an update that doesn't fix the broken update mechanism.

[flowl]

https://github.com/docker/for-mac/issues/6148 https://github.com/docker/for-mac/issues/6144

[igorkulman]

@flowl same problem here, I "solved" it by deleting Docker Deskop, using https://github.com/abiosoft/colima instead and never looking back.