![]() ![]() ![]() The -o option writes to a file instead of STDOUT. Yep! Bomb the crap out of Docker by going into the Docker -> Preferences menu and clicking that Reset icon.Īnd this works, but you will loose all your images and containers if you don’t take some steps to preserve them. I have found two ways to work around this issue of my Mac experiencing disk space issues as a result of testing with Docker. Since I am working with mainly the Oracle 12.1 image, which is in the 5+GB range, space is at a premium and so here’s to hoping they find a solution sooner than later as it is at a minimum inconvenient to have to do either one of these processes. “The qcow file is a block disk image that grows when unwritten blocks in the 64GB virtual device are written so the sparsity of writes due to ext4 disk layout causes an initially large increase in image size.” Here is the issue according to the Docker forums: So this is the impetus for the blog post today.Ī quick Google search shows that this issue is not new and is obviously still present in the most recent release as of this post. Deleting images or containers has no impact on this file. I’m sure I need to clean up some stuff myself, but that’s not the point of this post. On my MacBook Pro that consumes all of the remaining space I have on my hard drive, and SSD’s ain’t cheap. ~/Library/Containers//Data/64-linux/Docker.qcow2 Why you ask? Well, there is this file, Docker.qcow2 located right here: I really enjoy figuring out stuff to do with DOCKER, but I recently tweeted the following: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |