Docker Community Forums

Share and learn in the Docker community.

Reuse existing image stores


(Jean Helou) #1

This is not a bug but an improvement request

Expected behavior

When starting a docker container using docker for mac which was already started using docker-machine before and whose image files have not been deleted, the container should start immediately

Actual behavior

docker for mac downloads the image files again (and I assume stores them in a separate directory)

Information

OS X: version 10.11.3 (build: 15D21)
Docker.app: version v1.10.3-beta5
Running diagnostic tests:
[OK] docker-cli
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] lofs
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x
Docker logs are being collected into /tmp/20160331-134148.tar.gz.
Your unique id in bugsnag is: B8782C83-6640-4473-A217-C9C74348F192
Please quote this in all correspondence.

  • a reproducible case if this is a bug, Dockerfiles FTW

  • page URL if this is a docs issue or the name of a man page

  • host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )

Steps to reproduce the behavior

docker-machine start default
docker run ubuntu:latest
wait for a bit
docker rm -f ${the container id}
dicker machine stop default

start docker4mac
docker run ubuntu:latest


(Jean Helou) #2

Re-reading the documentation I think this failed to work for me because I used a vm named docker instead of default in docker-machine. The documentation states that images and containers from default will be copied.