beenull/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge pull request #21666 from thaJeztah/undeprecate-auto-generated-paths

Browse source 
Un-deprecate auto-creation of host directories for mounts
This commit is contained in:
David Calavera 2016-03-30 15:18:08 -07:00
commit 9d5c26bed2
3 changed files with 1 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/deprecated.md
View file

@ -133,17 +133,6 @@ The following double-dash options are deprecated and have no replacement:
docker ps --before-id docker ps --before-id
docker search --trusted 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 ### 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. 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.

3
docs/reference/run.md
View file

@ -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) --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**: > **Note**:
> When using systemd to manage the Docker daemon's start and stop, in the systemd > 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 > unit file there is an option to control mount propagation for the Docker daemon

2
docs/userguide/containers/dockervolumes.md
View file

@ -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 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 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 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 Docker volumes default to mount in read-write mode, but you can also set it to
be mounted read-only. be mounted read-only.