https://github.com/docker/roadmap/issues/183#issuecomment-748871985 https://github.com/docker/roadmap/issues/183#issuecomment-74... > Blocking outgoing network

https://github.com/docker/roadmap/issues/183#issuecomment-748871985 https://github.com/docker/roadmap/issues/183#issuecomment-74... > Blocking outgoing network connections to desktop.docker.com can keep you on on the functional 3.0.1 by not allowing the auto-upgrade to 'find' the broken 3.0.2 version, this can be used as a temporary patch. You'd need somethling like Little Snitch to achieve it, but at least you won't lose a Monday. I use Little Snitch, usually on "Alert Mode", and I almost breathe a sigh of relief whenever I block an automatic outgoing connection to an upgrade server. It can be distracting and annoying to block connections at a granularity to keep the application working correctly, and sometimes I get a bit fed up and just allow all connections, but usually temporarily. Since I even want to be consulted for outgoing network connections, you bet that I want to be consulted before a software upgrade!