By default, Docker for Mac ships with the default filesystem being aufs.This is a fairly antiquated filesystem and is quite slow if you deal with lots of files and filesystem reads and writes. Docker For Mac 1.13.0 brings support for macOS Sierra, now runs ARM & AARCH64 based Docker containers. Default storage driver as overlay2, Plugins support. I installed Docker 1.13 on macOS 10.10, logged in the docker 'machine' with screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty And did a df -h. It says I have a /dev/sda1 mounted on /var/lib/docker/overlay2 with 64 GB of disk space. /dev/sda1 62.7G 5.6G 54.0G 9% /var/lib/docker/overlay2 I had a few builds failing for 'no space left on device' so I suspect this is where all images end up going. What is not clear to me is the following: • what is this /dev/sda1. Is it a virtual image disk somewhere on my mac? If so, where? • Suppose I am running out of space and I want to store more images. How does one increase this disk space? Daniel's answer is right but I found an easier solution. In my case, I think I did migrate from docker-toolbox back in the days which locked by database to ~17G. I found it easier to follow these instructions: Note that this will delete your containers: • Stop docker for mac • rm ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 • Start docker for mac It seemed to work on my side. Mentions and commands that let you backup your containers before nuking your Docker.qcow2. I didn't use them since I didn't really care about my containers.
0 Комментарии
Оставить ответ. |
АвторНапишите что-нибудь о себе. Не надо ничего особенного, просто общие данные. Архивы
Март 2019
Категории |