Add documentation for new mount command (#4796)

The currently implementation uses sshfs (and FUSE) to mount.
It would be possible to make a Windows version, using Dokan.

Signed-off-by: Anders F Björklund <anders.f.bjorklund@gmail.com>
This commit is contained in:
Anders Björklund
2017-10-06 01:39:38 +02:00
committed by Misty Stanley-Jones
parent df45999813
commit 9ce2b2e893

View File

@@ -0,0 +1,49 @@
---
description: Mount directory from machine
keywords: machine, mount, subcommand
title: docker-machine mount
---
Mount directories from a machine to your local host, using `sshfs`.
The notation is `machinename:/path/to/dir` for the argument; you can also supply an alternative mount point (default is the same dir path).
## Example
Consider the following example:
```none
$ mkdir foo
$ docker-machine ssh dev mkdir foo
$ docker-machine mount dev:/home/docker/foo foo
$ touch foo/bar
$ docker-machine ssh dev ls foo
bar
```
Now you can use the directory on the machine, for mounting into containers.
Any changes done in the local directory, will be reflected in the machine too.
```none
$ docker run -v /home/docker/foo:/tmp/foo busybox ls /tmp/foo
bar
$ docker touch foo/baz
$ docker run -v /home/docker/foo:/tmp/foo busybox ls /tmp/foo
bar
baz
```
The files are actually being transferred using `sftp` (over an ssh connection),
so this program ("sftp") needs to be present on the machine - but it usually is.
To unmount the directory again, you can use the same options but the `-u` flag.
You can also call `fuserunmount` (or `fusermount -u`) commands directly.
```none
$ docker-machine mount -u dev:/home/docker/foo foo
$ rmdir foo
```
**Note that files are actually being stored on the machine, *not* on the host.**
So make sure to make a copy of any files you want to keep, before removing it!