From 72425820ec9ac08f7501e3e931b85b84aa7a7b36 Mon Sep 17 00:00:00 2001 From: Docker Library Bot Date: Wed, 31 Aug 2016 16:46:59 -0700 Subject: [PATCH] Run update.sh --- docker/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docker/README.md b/docker/README.md index 277f8f09f..9daa3c480 100644 --- a/docker/README.md +++ b/docker/README.md @@ -34,6 +34,8 @@ If you are still convinced that you need Docker-in-Docker and not just access to ## Start a daemon instance +**IMPORTANT:** this image defaults to `--storage-driver=vfs`, which will be very slow and inefficient (but is the only driver which is guaranteed to work regardless of your underlying filesystem). Which driver you should use varies depending on your needs, but a good rule of thumb is that your DinD instance should be using the same driver as your host (which can be seen under `Storage Driver` in the output of `docker info`). See the "Custom daemon flags" section below for how to specify your storage driver. + ```console $ docker run --privileged --name some-docker -d docker:1.8-dind ``` @@ -132,7 +134,7 @@ Server: ## Custom daemon flags ```console -$ docker run --privileged --name some-devicemapper-docker -d docker:dind --storage-driver=devicemapper +$ docker run --privileged --name some-overlay-docker -d docker:dind --storage-driver=overlay ``` ## Where to Store Data