From 0f70f53826ac311ca1653827c0d6bc170f300e84 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Wed, 30 Mar 2016 15:00:09 -0700 Subject: [PATCH] Un-deprecate auto-creation of host directories for mounts Auto-creation of host-directories was marked deprecated in Docker 1.9, but was decided to be too much of an backward-incompatible change, so it was decided to keep the feature. Signed-off-by: Sebastiaan van Stijn --- docs/deprecated.md | 11 ----------- docs/reference/run.md | 3 --- docs/userguide/containers/dockervolumes.md | 2 +- 3 files changed, 1 insertion(+), 15 deletions(-) diff --git a/docs/deprecated.md b/docs/deprecated.md index d2acf31f67..f1c1fb0a77 100644 --- a/docs/deprecated.md +++ b/docs/deprecated.md @@ -133,17 +133,6 @@ The following double-dash options are deprecated and have no replacement: docker ps --before-id docker search --trusted -### Auto-creating missing host paths for bind mounts -**Deprecated in Release: v1.9** - -**Target for Removal in Release: 1.11** - -When creating a container with a bind-mounted volume-- `docker run -v /host/path:/container/path` -- -docker was automatically creating the `/host/path` if it didn't already exist. - -This auto-creation of the host path is deprecated and docker will error out if -the path does not exist. - ### Interacting with V1 registries Version 1.9 adds a flag (`--disable-legacy-registry=false`) which prevents the docker daemon from `pull`, `push`, and `login` operations against v1 registries. Though disabled by default, this signals the intent to deprecate the v1 protocol. diff --git a/docs/reference/run.md b/docs/reference/run.md index 7edcd7e16a..62cd5c888a 100644 --- a/docs/reference/run.md +++ b/docs/reference/run.md @@ -1414,9 +1414,6 @@ The example below mounts an empty tmpfs into the container with the `rw`, --volumes-from="": Mount all volumes from the given container(s) -> **Note**: -> The auto-creation of the host path has been [*deprecated*](../deprecated.md#auto-creating-missing-host-paths-for-bind-mounts). - > **Note**: > When using systemd to manage the Docker daemon's start and stop, in the systemd > unit file there is an option to control mount propagation for the Docker daemon diff --git a/docs/userguide/containers/dockervolumes.md b/docs/userguide/containers/dockervolumes.md index 5225ac02d9..9c960d1fe9 100644 --- a/docs/userguide/containers/dockervolumes.md +++ b/docs/userguide/containers/dockervolumes.md @@ -144,7 +144,7 @@ Mounting a host directory can be useful for testing. For example, you can mount source code inside a container. Then, change the source code and see its effect on the application in real time. The directory on the host must be specified as an absolute path and if the directory doesn't exist the Engine daemon automatically -creates it for you. This auto-creation of the host path has been [*deprecated*](../../deprecated.md#auto-creating-missing-host-paths-for-bind-mounts). +creates it for you. Docker volumes default to mount in read-write mode, but you can also set it to be mounted read-only.