
Docker For Mac Stuck On Starting
I have the latest Docker for Mac installed, and I'm running into a problem where it appears that docker-compose up is stuck in a Downloading state for one of the containers: ± master ✗ → docker-compose up --build Pulling cardapp (quay.io/company/container:prod). Prod: Pulling from company/container somehash: Already exists somehash: Already exists somehash: Already exists somehash: Already exists somehash: Pulling fs layer somehash: Already exists somehash: Already exists somehash: Downloading [=================================================> ] 234.6 MB/239.3 MB somehash: Download complete somehash: Download complete ^^ this is literally what it looks like on my command line. Stopping and starting hasn't helped, it immediately outputs this same output. I've tried to rm the container but I guess it doesn't yet exist, it returns the output No stopped containers.
Jun 21, 2018 - The IBM DB2 Developer Community Edition Docker installation on my Mac is hanging on repeated attempts. The install gets through the. Docker for Mac now ships with Kubernetes built-in! Let's explore why this matters, a history of developer tooling & my first impressions as I kick the tyres. Hp printer driver for mac samsung ml-2510. Containers (which normally means Linux containers) were not available on Windows or Mac when Docker began its story as a spin-out from.
--force-recreate also gets stuck in the same place. And perhaps I'm not googling for the right terminology but I haven't found anything useful to try - any pointers?
Docker For Mac has really changed how I work: I now use it for all my linux-related developments. The integration is OS X is really well done and it’s really perfect for a development environment. The only problem is that Docker For Mac uses a file called Docker.qcow2 that takes more and more disk space as time passes (mine got to 20GB). Deleting images or containers does not decrease the size of this file. The issue has been reported several times (like for instance), but no official fix exists yet, even with this week’s release of Docker 1.12.1. After discussing with a Docker employee working on Docker For Mac and Docker For Windows in Paris during last, it seems that the only solution right now is to simply delete this file.

However deleting it will also remove all your containers and images. Here is a small script that will do that for you, and you can give it some images that you would like to keep as arguments.