mirror of https://github.com/docker/docs.git
Included npipe to documentation (#7427)
This commit is contained in:
parent
07360ef578
commit
500b9b166d
|
@ -1924,7 +1924,7 @@ volumes:
|
||||||
The long form syntax allows the configuration of additional fields that can't be
|
The long form syntax allows the configuration of additional fields that can't be
|
||||||
expressed in the short form.
|
expressed in the short form.
|
||||||
|
|
||||||
- `type`: the mount type `volume`, `bind` or `tmpfs`
|
- `type`: the mount type `volume`, `bind`, `tmpfs` or `npipe`
|
||||||
- `source`: the source of the mount, a path on the host for a bind mount, or the
|
- `source`: the source of the mount, a path on the host for a bind mount, or the
|
||||||
name of a volume defined in the
|
name of a volume defined in the
|
||||||
[top-level `volumes` key](#volume-configuration-reference). Not applicable for a tmpfs mount.
|
[top-level `volumes` key](#volume-configuration-reference). Not applicable for a tmpfs mount.
|
||||||
|
|
|
@ -22,6 +22,7 @@ container layer. This means that:
|
||||||
Docker has two options for containers to store files in the host machine, so
|
Docker has two options for containers to store files in the host machine, so
|
||||||
that the files are persisted even after the container stops: _volumes_, and
|
that the files are persisted even after the container stops: _volumes_, and
|
||||||
_bind mounts_. If you're running Docker on Linux you can also use a _tmpfs mount_.
|
_bind mounts_. If you're running Docker on Linux you can also use a _tmpfs mount_.
|
||||||
|
If you're running Docker on Windows you can also use a _named pipe_.
|
||||||
|
|
||||||
Keep reading for more information about these two ways of persisting data.
|
Keep reading for more information about these two ways of persisting data.
|
||||||
|
|
||||||
|
@ -100,6 +101,10 @@ mounts is to think about where the data lives on the Docker host.
|
||||||
information. For instance, internally, swarm services use `tmpfs` mounts to
|
information. For instance, internally, swarm services use `tmpfs` mounts to
|
||||||
mount [secrets](/engine/swarm/secrets.md) into a service's containers.
|
mount [secrets](/engine/swarm/secrets.md) into a service's containers.
|
||||||
|
|
||||||
|
- **[named pipes](https://docs.microsoft.com/en-us/windows/desktop/ipc/named-pipes)**: An `npipe`
|
||||||
|
mount can be used for communication between the Docker host and a container. Common use case is
|
||||||
|
to run a third-party tool inside of a container and connect to the Docker Engine API using a named pipe.
|
||||||
|
|
||||||
Bind mounts and volumes can both be mounted into containers using the `-v` or
|
Bind mounts and volumes can both be mounted into containers using the `-v` or
|
||||||
`--volume` flag, but the syntax for each is slightly different. For `tmpfs`
|
`--volume` flag, but the syntax for each is slightly different. For `tmpfs`
|
||||||
mounts, you can use the `--tmpfs` flag. However, in Docker 17.06 and higher,
|
mounts, you can use the `--tmpfs` flag. However, in Docker 17.06 and higher,
|
||||||
|
|
Loading…
Reference in New Issue