Report of annoying behaviour

Whenever I run out of disc-space when building an image I get:
ERROR: failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF
Then docker cannot even remove these images. Because (My guess) docker needs discs pace to remove the image. Either way it is bugging out when I try to delete in docker GUI or when I try

docker image prune
WARNING! This will remove all dangling images.
Are you sure you want to continue? [y/N] Y
........................... nothing happens stays frozen on empty line.

My suggestion:
End the build process before running out of space so I don’t have to delete install whole of docker when it happens. Or just pause the environment somehow until more space is made available.

Anyhow, would be much appreciated if this could be addressed!
thanks

Hello!
When Docker runs out of disk space mid-build, it can crash the daemon and cause errors like rpc error: code = Unavailable desc = error reading from server: EOF. This often freezes cleanup commands like docker image prune. To fix this, restart Docker, then force-remove containers and images using docker rm -f $(docker ps -aq) and docker rmi -f $(docker images -q). To avoid this in the future, use multi-stage builds, monitor disk space in scripts, and automate regular cleanups with docker system prune -a --force. Also, consider sharing your idea of pausing builds when low on space on the Docker Buildx GitHub page—it’s a smart suggestion.

The right place to report bugs and improvement ideas in Docker Desktop for Windows is this GitHub project: