Interestingly, they appear to be using Sparkle [0]. Oddly, stephen-turner claims that Sparkle is part of the reason it's taking some time to fix the issue. Dir

Interestingly, they appear to be using Sparkle [0]. Oddly, stephen-turner claims that Sparkle is part of the reason it's taking some time to fix the issue. Direct quote: > As said above, we're working on this: we're planning to download the update in the background and then give the user the choice whether to update to it on next start. It's taken a little longer than we hoped because the Sparkle framework we use on Mac doesn't expect that workflow: once the update has been downloaded, it wants to apply it without confirmation at next shutdown. We are keen to retain the invisible download but give the user a choice whether to apply it later. It's hard to understand why they're struggling with a problem that seems to be solved by every other app that uses Sparkle... - [0] https://github.com/docker/roadmap/issues/183#issuecomment-797412882 https://github.com/docker/roadmap/issues/183#issuecomment-79...