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 <github@gone.nl>
(cherry picked from commit 0f70f53826ac311ca1653827c0d6bc170f300e84)
| ... | ... |
@@ -133,17 +133,6 @@ The following double-dash options are deprecated and have no replacement: |
| 133 | 133 |
docker ps --before-id |
| 134 | 134 |
docker search --trusted |
| 135 | 135 |
|
| 136 |
-### Auto-creating missing host paths for bind mounts |
|
| 137 |
-**Deprecated in Release: v1.9** |
|
| 138 |
- |
|
| 139 |
-**Target for Removal in Release: 1.11** |
|
| 140 |
- |
|
| 141 |
-When creating a container with a bind-mounted volume-- `docker run -v /host/path:/container/path` -- |
|
| 142 |
-docker was automatically creating the `/host/path` if it didn't already exist. |
|
| 143 |
- |
|
| 144 |
-This auto-creation of the host path is deprecated and docker will error out if |
|
| 145 |
-the path does not exist. |
|
| 146 |
- |
|
| 147 | 136 |
### Interacting with V1 registries |
| 148 | 137 |
|
| 149 | 138 |
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. |
| ... | ... |
@@ -1415,9 +1415,6 @@ The example below mounts an empty tmpfs into the container with the `rw`, |
| 1415 | 1415 |
--volumes-from="": Mount all volumes from the given container(s) |
| 1416 | 1416 |
|
| 1417 | 1417 |
> **Note**: |
| 1418 |
-> The auto-creation of the host path has been [*deprecated*](../deprecated.md#auto-creating-missing-host-paths-for-bind-mounts). |
|
| 1419 |
- |
|
| 1420 |
-> **Note**: |
|
| 1421 | 1418 |
> When using systemd to manage the Docker daemon's start and stop, in the systemd |
| 1422 | 1419 |
> unit file there is an option to control mount propagation for the Docker daemon |
| 1423 | 1420 |
> itself, called `MountFlags`. The value of this setting may cause Docker to not |
| ... | ... |
@@ -144,7 +144,7 @@ Mounting a host directory can be useful for testing. For example, you can mount |
| 144 | 144 |
source code inside a container. Then, change the source code and see its effect |
| 145 | 145 |
on the application in real time. The directory on the host must be specified as |
| 146 | 146 |
an absolute path and if the directory doesn't exist the Engine daemon automatically |
| 147 |
-creates it for you. This auto-creation of the host path has been [*deprecated*](../../deprecated.md#auto-creating-missing-host-paths-for-bind-mounts). |
|
| 147 |
+creates it for you. |
|
| 148 | 148 |
|
| 149 | 149 |
Docker volumes default to mount in read-write mode, but you can also set it to |
| 150 | 150 |
be mounted read-only. |