Free AI web copilot to create summaries, insights and extended knowledge, download it at here

1223

Abstract

h3></div> <div><p>medium.com</p></div> </div> <div> <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/1*Pp4DNqrrrz6ZFjs-VAW5hw.png)"></div> </div> </div> </a> </div><p id="ea86">But something happens after running Docker images for a while. The disk footprint starts to build up, and if you’re working on a machine with 128GB or fewer, it can happen pretty quickly. All of those intermediate containers and unused images and volumes start to add up.</p><p id="817e">It’s really nice to work on a machine with a larger hard drive, but if you run out of space and you just need to start over, here is how to do it.</p><blockquote id="3347"><p><b>Warning: This will delete all containers, images, and (optionally) volumes. Run these commands at your own risk.</b></p></blockquote><figure id="7491"><img src="https://cdn-images-1.readmedium.com/v2/resize:fit:800/0*wCBTtHVWUu57jzwW.jpg"><figcaption>Blow it up</figcaption></figure><p id="1a7d">If you are running at least version 1.25 of the Client and Daemon API, you can run <a href="https://docs.docker.com/engine/reference/commandline/syste

Options

m_prune/">the prune command</a>:</p><p id="cba3" type="7">docker system prune</p><p id="034e">By default, this does not remove volumes. So if you also want to do that, you can add an optional flag:</p><p id="4242" type="7">docker system prune -a --volumes</p><h2 id="98cd">Older Versions of Docker</h2><p id="ab97">If you are running an older version of Docker, and you don’t have this handy command available, you can run this script to effectively do the same thing:</p> <figure id="cc60"> <div> <div>

            <iframe class="gist-iframe" src="/gist/timjonesdev/5ea97bb10eddd311e57b1a5a0c0f9432.js" allowfullscreen="" frameborder="0" height="undefined" width="undefined">
          </div>
        </div>
    </figure></iframe></div></div></figure><p id="90ce">Phew! It sure feels good to get that space back. Unfortunately, my experience has been that if I need to do this once, I usually need to do it somewhat frequently. It’s annoying when Docker has to re-download images again, but cest la vie.</p><p id="3f1b">I hope this is helpful for those of us that find disk space hard to come by during development. Thanks for reading!</p></article></body>

Take Your Disk Space Back from Docker

Docker is amazing. It has absolutely revolutionized the development, deployment, and management of applications. I use it every single day.

Gone are the days of downloading some version of Postgres or MySQL, running through the install instructions, and manually setting up the database to accept connections from your app. Now we can just pull the image, seed the database with some initialization scripts, and voila! We’re up and running in no time, with very little busy work. It’s fast, repeatable, and comparatively painless.

Go Modules with Private Git Repositories

How to configure Go Modules to work with private Git Repositories, with examples for both local development and Docker.

medium.com

But something happens after running Docker images for a while. The disk footprint starts to build up, and if you’re working on a machine with 128GB or fewer, it can happen pretty quickly. All of those intermediate containers and unused images and volumes start to add up.

It’s really nice to work on a machine with a larger hard drive, but if you run out of space and you just need to start over, here is how to do it.

Warning: This will delete all containers, images, and (optionally) volumes. Run these commands at your own risk.

If you are running at least version 1.25 of the Client and Daemon API, you can run the prune command:

docker system prune

By default, this does not remove volumes. So if you also want to do that, you can add an optional flag:

docker system prune -a --volumes

Older Versions of Docker

If you are running an older version of Docker, and you don’t have this handy command available, you can run this script to effectively do the same thing:

Phew! It sure feels good to get that space back. Unfortunately, my experience has been that if I need to do this once, I usually need to do it somewhat frequently. It’s annoying when Docker has to re-download images again, but cest la vie.

I hope this is helpful for those of us that find disk space hard to come by during development. Thanks for reading!