github.com/jogo/docker@v1.7.0-rc1/docs/sources/experimental/plugins_volume.md (about) 1 page_title: Experimental feature - Volume plugins 2 page_keywords: experimental, Docker, plugins, volume 3 4 # Experimental: Docker volume plugins 5 6 Docker volume plugins enable Docker deployments to be integrated with external 7 storage systems, such as Amazon EBS, and enable data volumes to persist beyond 8 the lifetime of a single Docker host. See the [plugin documentation](/experimental/plugins) 9 for more information. 10 11 This is an experimental feature. For information on installing and using experimental features, see [the experimental feature overview](experimental.md). 12 13 # Command-line changes 14 15 This experimental features introduces two changes to the `docker run` command: 16 17 - The `--volume-driver` flag is introduced. 18 - The `-v` syntax is changed to accept a volume name a first component. 19 20 Example: 21 22 $ docker run -ti -v volumename:/data --volume-driver=flocker busybox sh 23 24 By specifying a volume name in conjunction with a volume driver, volume plugins 25 such as [Flocker](https://clusterhq.com/docker-plugin/), once installed, can be 26 used to manage volumes external to a single host, such as those on EBS. In this 27 example, "volumename" is passed through to the volume plugin as a user-given 28 name for the volume which allows the plugin to associate it with an external 29 volume beyond the lifetime of a single container or container host. This can be 30 used, for example, to move a stateful container from one server to another. 31 32 The `volumename` must not begin with a `/`. 33 34 # API changes 35 36 The container creation endpoint (`/containers/create`) accepts a `VolumeDriver` 37 field of type `string` allowing to specify the name of the driver. It's default 38 value of `"local"` (the default driver for local volumes). 39 40 # Related GitHub PRs and issues 41 42 - [#13161](https://github.com/docker/docker/pull/13161) Volume refactor and external volume plugins 43 44 Send us feedback and comments on [#13420](https://github.com/docker/docker/issues/13420), 45 or on the usual Google Groups (docker-user, docker-dev) and IRC channels.