Does that also remove any existing containers and maybe even Docker-managed volumes?
(I feel that one always should be able to re-create containers from images, like by storing Dockerfiles in some source control and not altering the container directly. And that one should backup any data volumes. But not everyone ensures both.)
Probably! I generally don’t mind doing that - we check our Dockerfile and docker-compose.yml into source control, and I liberally use docker-clean to ensure that I’ve got the latest images.
Made an account specifically to comment here; I finally figured out a solution after 3 days of struggle.
I was having the same issue with Docker Desktop v4.12.0 on my 2017 MacBook Pro. I fully re-installed Docker at least 5 times, and I updated to macOS Monterey 12.6 to try to resolve the issue. nothing worked except for downloading the latest Docker.dmg file and installing via the following command:
