docker
Docker updates for macOS High Sierra
Despite turning off automatic updates
Docker keeps telling me updates aren't available. It sends these warnings in pairs, and they don't even mention they are for Docker.
Can you make just one more update to fix the automatic updates feature so it doesn't check when the option is turned off? The pairs of system modal dialog boxes come up more than once a day.
Hi @idontusenumbers could you upload diagnostics data (Troubleshoot -> Run Diagnostics and -> Upload) and attach the diagnostics id so we get a better understanding of your installation? Thanks.
Thanks, version 2.3.7.0 indeed shows this warning. We started to remove macOS 10.13 support beginning with version 2.3.6.0.
You could manually download version 2.3.5.0 from here: https://docs.docker.com/docker-for-mac/edge-release-notes/#docker-desktop-community-2350
It's still technically possible to install and run newer versions, but we stop looking into issues on 10.13.
Are you suggesting downgrading to before the bug was introduced or what is the significance of 2.3.5.0?
Are there any downsides to going back to version 2.3.5.0? I keep getting these messages daily too.
Same problem here. Auto updates disabled, popup still comes every day.
In addition: there is no identification at all that this notification comes from Docker. Had to restort to some deep digging to find the owning process of the window..
If you do not release a patch for this, what URL can I block to make sure you cannot reach your update servers?
And since there is no indexable text for other users to google this ticket, adding it here: There is an update but you are on OS X 10.13 or an earlier version. Upgrade to the latest version of macOS to install it
When I first encountered this unlabeled pop-up, I assumed it was from Apple. Some of Apple's programs (e.g., Numbers) continually hound me with reminders to upgrade. These kinds of dialogs need "Don't show me this again" checkboxes.
Funny thing is, these upgrade notices are trying to be helpful but they're not. OS X 10.14 is not supported on my hardware, so I cannot upgrade. (Same story for the Numbers update.)
Nevertheless, it seems like the "Automatically check For updates" preferences is not being respected. This might indicate a bug that still exists in the current version. Even if you don't plan any changes for 10.13, this should be investigated.
If you do not release a patch for this, what URL can I block to make sure you cannot reach your update servers?
I checked the log on my DNS server and it seems to be connecting to desktop.docker.com. I'm currently blocking the domain and it generates an error when manually checking for updates but I will have to wait until tomorrow to see if the dialogs are gone.
I'm in the same boat as other users, the machine where I run my containers won't get any more updates from Apple, so I know the OS in unsupported but there is no point getting two daily reminders about it.
Update: 10 days later it seems to be working. I haven't had a any new "update" dialogs.
but I will have to wait until tomorrow to see if the dialogs are gone.
@Diegus83, did this work?
Q. "There's a bug in the program in that it keeps on telling me to update when that's not possible." A. "That's an old version of the program; we won't fix bugs in that version anymore."
Still hoping for some relief here.
I had the same poor experience with this popup: had to use Xcode tools in order to identify its owner process and it keeps reappearing despite the auto update setting being off (on newer Docker versions; on 2.3.5.0 it seems to respect the setting so far).
Please make this disappear. Getting these popups every damn day with updates check disabled is just nonsense.
After many weeks of frustration caused by this window popping up multiple times per day I decided to Google the problem and see if I could find an answer. I had no idea what application was causing the continued errors since, as @stromnet has pointed out, there is nothing in the error to indicate that this is related to Docker.
I found a post on StackExchange (Unexplained and persistent “OS X 10.13 is not supported” dialog) that suggested the error was caused by Docker. I disabled updates in Docker Desktop and assumed that the problem would go away.
When the errors continued to occur, I assumed that the Stack Exchange post was incorrect and started looking at other applications that might be causing the issue. After several more weeks of dealing with the pop-up error messages, I decided to try once again to find an answer and ultimately came upon this issue on GitHub.
Like @barkofdelight, I am unable to upgrade my current version of OS X.
The error message is itself is flawed - if there had been some indication that this was Docker related, it would have saved considerable time in trying to find a solution. The fact that the errors occur even when updates are disabled is obviously a problem. The fact that these messages are sent multiple times per day is disruptive. The process of changing focus from the currently running application to the error window is also disruptive.
I guess the only options are to block desktop.docker.com in my hosts file or to downgrade to 2.3.5.0 - though I don't understand the full ramifications of either of these two suggestions.
@pierow2k For what is worth, I'm still running with desktop.docker.com blocked via the host file and had encountered no issues so far when restarting the containers, or pulling new images.
Thanks for the update @Diegus83 . I have (begrudgingly) added desktop.docker.com to my hosts file.
It's still technically possible to install and run newer versions, but we stop looking into issues on 10.13.
I haven't done extensive testing but I've downloaded and installed the latest version of Docker Desktop on High Sierra. It installs without any issue and I'm still able to run containers.
The option to automatically check for updates has disappeared and manually checking for updates tells me Docker is up to date rather than my OS not being supported. I don't know if the popup will return when another version is released.
The option to automatically check for updates has disappeared and manually checking for updates tells me Docker is up to date rather than my OS not being supported. I don't know if the popup will return when another version is released.
Alas... the popup returned with the latest 3.1.0 update. Manually updating clears the popup again but that will only work for so long. Having the ability to disable the check for updates (and for it to work as expected) would be most welcome.
It's still technically possible to install and run newer versions, but we stop looking into issues on 10.13.
Given this, might it be feasible to update this dialog to allow upgrading to a newer version, with the caveat that it won't be supported? Like others, I'm on a machine that won't be upgraded past 10.13, but would like to still use the latest Docker without this persistent dialog.
seriously, give us the option to disable checking for updates. better yet, sign your dialogue so it's clear Docker is causing this. I'm not updating my stable OS and trusted workstation just because Docker prefers to run on a newer one. plus, manually checking for updates tells me I'm using the newest version anyway. which I am.
I guess the only options are to block
desktop.docker.comin myhostsfile
This has solved this for me also.
Edit: Caveat: See below, I did this but perhaps it didn't solve the problem alone
I guess the only options are to block
desktop.docker.comin myhostsfileThis has solved this for me also.
Does not help here.. at least not pointing it to 127.0.0.1, did you use something else?
Does not help here.. at least not pointing it to 127.0.0.1, did you use something else?
🤔 Maybe it was something else then. I might have downgraded - I remember looking to downgrade (and maybe uninstalling in preparation of) but found the suggested "2.3.5.0" didn't exist on the page linked to above. I'm running 2.5.0.1 now, which seems to be the last pre-3. build so probably didn't. Maybe uninstalling and reinstalling (with the domain blocked, so that it never sees that an update is available to spam messages over) did the trick.
(I also appear to have accidentally added the hosts file as 128.0.0.1 desktop.docker.com but can't imagine that helped).
It seems they chose to pretend like Docker 2.3.5.0 never existed -- yes, it vanished from official download pages. However, it is still accessible through direct URL if you want to give it a try: https://desktop.docker.com/mac/edge/47376/Docker.dmg
Does not help here.. at least not pointing it to 127.0.0.1, did you use something else?
No. It has been working like that ever since. Never downgraded or changed versions. Try pinging the address from a Terminal. If it is still resolving check the line you added for typos, flush the DNS cache and try restarting the Mac. This are the last lines of my hosts file.
# Added by Docker Desktop
# To allow the same kube context to work on the host and the container:
127.0.0.1 kubernetes.docker.internal
# End of section
# Avoid Docker desktop updates notifications
127.0.0.1 desktop.docker.com
Tried 128.0.0.1 yesterday, today got popup again. And yes, it resolves properly (at least ping in terminal). Also tried restarting Docker Desktop, did not make any difference.
Installed 3.2.2 instead, no warnings about unsupported, and at least basic operation seems to be working fine. Edit: Had one hickup in volume mount.. One of 4 identical containers got stuck reading from host-mounted fs (fuse, not gprc; disabled that long ago since it worked really slow. Perhaps better nowadays?). Have not reproduced yet.
Also tried restarting Docker Desktop, did not make any difference
The DNS resolution happens in macOS, not in the docker app so restarting the app should not change anything. If you edited the right file (/etc/hosts) and added the right line (check the use of spaces vs tabs, etc) it should work after restarting the Mac.
After repeated problems with 3.2.2 and FUSE not pickup in changes in files on host system (config watcher in container not realising file was changed; works perfectly fine in 2.5.x), I reverted back to 2.5.0.1.
Unfortunately the "upgrade" popup appeared directly after installing, even if desktop.docker.com is pointing to 127.0.0.1. Perhaps cached from previous install or something..
Edit: oh, and tried to use grpc too.. awfully slow still, unusable.
Sadly, the popup actually seems to come more often now... Several times per day..
@stromnet the popup goes away until the next Docker release if you update manually. also, localhost is 127.0.0.1 not 128. i'm stuck with my OS version, can't/won't upgrade, so this popup bothers me a lot.
Of course localhost is 127. and not 128, but that should make no difference for this particular purpose.
Not sure why it didn't "bite", despite sending HUP to mDNSResponder and dscacheutil -flushcache etc (did not try reboot though), but after doing the change in my local DNS instead, the spammy popups has finally stopped!
Good to have working docker back, even if old version.