Unable to update from 3.3.1 to newer version

[flowl]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• 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.