Cleaning up Docker For Mac (Docker is eating my disk space)

  • 23 Jun, 2017

The disk space on my mac is too short since i start to use docker.  Using the management tools i found the file Docker.qcow2 with the size of 41,5 GB.

Searching for a solution i found the following:

“ Docker For Mac uses a file called Docker.qcow2 that takes more and more disk space as time passes. Deleting images or containers does not decrease the size of this file.“

The script bellow do the job an keep your selected images.

#!/bin/bash # Copyright 2017 Théo Chamley # Permission is hereby granted, free of charge, to any person obtaining a copy of # this software and associated documentation files (the "Software"), to deal in the Software # without restriction, including without limitation the rights to use, copy, modify, merge, # publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons # to whom the Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in all copies or # substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING # BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND # NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, # DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, IMAGES=$@ echo "This will remove all your current containers and images except for:" echo ${IMAGES} read -p "Are you sure? [yes/NO] " -n 1 -r echo    # (optional) move to a new line if [[ ! $REPLY =~ ^[Yy]$ ]] then     exit 1 fi TMP_DIR=$(mktemp -d) pushd $TMP_DIR >/dev/null open -a Docker echo "=> Saving the specified images" for image in ${IMAGES}; do     echo "==> Saving ${image}"     tar=$(echo -n ${image} | base64)     docker save -o ${tar}.tar ${image}     echo "==> Done." done echo "=> Cleaning up" echo -n "==> Quiting Docker" osascript -e 'quit app "Docker"' while docker info >/dev/null 2>&1; do     echo -n "."     sleep 1 done; echo "" echo "==> Removing Docker.qcow2 file" rm ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 echo "==> Launching Docker" open -a Docker echo -n "==> Waiting for Docker to start" until docker info >/dev/null 2>&1; do     echo -n "."     sleep 1 done; echo "" echo "=> Done." echo "=> Loading saved images" for image in ${IMAGES}; do     echo "==> Loading ${image}"     tar=$(echo -n ${image} | base64)     docker load -q -i ${tar}.tar || exit 1     echo "==> Done." done popd >/dev/null rm -r ${TMP_DIR}

Usage : .sh

Sample : ./CleanDocker.sh websphere-liberty ibmcom/db2express-c

The original post on this link: https://blog.mrtrustor.net/post/clean-docker-for-mac/

Related Posts

How to Use Podman with the GitHub MCP Server: Fixing the ENOENT Error on IBM Bob

  • 17 Jun, 2026

If you are exploring the new world of the Model Context Protocol (MCP) and trying to install the GitHub MCP server on IBM Bob, there is a good chance the documentation pointed you toward Docker. But what if you use Podman as your open-source, daemonless alternative? In theory, Podman's command compatibility should make the transition seamless. In practice, AI tools or managers like Bob/VS Code can run into unexpected environment issues. In this post, we will look at how to properly configure Podman for the GitHub MCP Server and, more importantly, how to resolve the persistent command-not-found (ENOENT) error, even after setting up terminal aliases. The Initial Plan: Creating a Docker Ali

How to Use Podman with the GitHub MCP Server: Fixing the ENOENT Error on IBM BobRead More

Docker grace period ends on January 31

  • 26 Jan, 2022

I received an email yesterday from Docker. It's a reminder about the end of grace period. Hello, As a reminder you’re receiving this email because on August 31, 2021 we updated the terms(https://email.notify.docker.com/c/eJyFj0FuxCAMRU9DdkRgknSyyGKkaq5ROWAImgARIRP19iVtF91VsmTp2fb30w9DWQbP4EAEBJ6AXJQt9YaY8UN7Q3VCEDEOhFT8fazNUkKbc6hWaZRuxA4jgOhlBZkG-6U3czwI0dYOVzTotpWw7U3cGj1rnef5xqGAlh2vtP5Dvx7zr7LfiU-Q75ZfXxNFlokCxMPU4SvjQGDb0LjL1fr3NheTQ8UzBR1M9XMYq2ij7ZBgMlyKQ8Ueo-xTQr79wT0fWVOHF3BGbPD0p-tRqzC9cl1RDu2v2HbZM936AvzFbcY) applicable to the Docker products or services you use. On January 31, 2022, the grace period ends for free commercial use of Docker Desktop in larger enterprises. Companie

Docker grace period ends on January 31Read More

A rootless Pod for wordpress

  • 07 Dec, 2021

Podman Pods are very similar to Kubernetes pods in a way that they can have more than one container. Every Podman pod contains one infra container by default. This container is responsible for associating the names space with the pod and allowing podman to connect the containers to another pod. Create a Pod using Podman The first step is to create a Pod using podman: sudo podman pod create –name For our example we will create a pod with the name wp-pod sudo podman pod create -p 8080:80 --name wp-pod After creating the Pod you can see the infra container using the command: sudo podman pod ps -a --pod Note that host port 8080 has been redirected to port 80 of the pod. Pod port settin

A rootless Pod for wordpressRead More