Products Cloud Native Applications Hyperconverged Infrastructure Software-Defined Storage Strategy vSAN

vSphere Docker Volume Service is now Docker Certified!

We are happy to announce that VMware has joined Docker Certification Program and vSphere Docker Volume Service (vDVS) plugin is now available on Docker Store!

Docker Certified

VMware’s inclusion into the program indicates that vSphere Docker Volume Service has been tested and verified by Docker, confirming to customers that the vSphere Docker Volume plugin has been evaluated for security and is supported and built according to best practices.

Simplified installation workflow with a managed plugin

Docker introduced Managed Plugin System in 1.13 which makes extending Docker capabilities extraordinarily easy. No more systemd tricks! Please note that you need to use Docker 1.13/17.03 and above.

Let’s quickly take a look at how easy it is to install and configure vSphere Docker Volume Service once it’s available as a managed plugin.

Here are the setup requirements for the following demonstration –

  • Docker Host (VM) running Docker 1.13/17.03 and above
  • vSphere ESXi 6.0+
  • vSphere Storage (VSAN, VMFS or NFS) for ESXi host


Step 1 – Log into Docker Host(VM) and install the plugin from Docker store by specifying “–grant-all-permissions” option. This option can be omitted to choose permissions interactively. You can customize the plugin name using “–alias” option.


Let’s verify the plugin is installed correctly and ready for use.


Step 2 – Log into ESXi host and download the latest release of vDVS driver VIB on ESXi and initiate the install by specifying the full path to the VIB.


Step 3 – On Docker Host(VM), let’s create a volume with default values i.e. default volume size = 100MB.


Step 4 – On ESXi host, the administrator can manage volumes available in the system effectively using the admin CLI.


What’s next in vSphere Docker Volume Service?

After announcing the beta of vSphere Docker Volume Service in DockerCon 2016, we have been steadily releasing new features and addressing customer feedback in the existing features at a monthly release cadence. It offers the following benefits to IT administrators and application developers –

  • Proven Persistent Shared Storage: You can now use any VMware supported enterprise class storage backed by vSAN, VMFS and NFS
  • Multitenancy, Security and Access Control: vSphere administrators can effortlessly set access permissions for shared storage across hosts, datastores and VMs from a single location
  • Operational Consistency & Simplicity: Zero Configuration, zero credential management. It is easy to deploy and manage
  • Self Service Operations: Use Docker APIs to manage volume lifecycle while maintaining administrator control over consumption
  • 100% Docker Compatible and supports high availability with Docker Swarm
  • Supports Storage Policy Based Management for Containers

In future blogs, we will dig deeper into some of the features mentioned above. Stay tuned!

If you are interested in contributing code or have any questions or feedback, you can reach us at


6 comments have been added so far

  1. This appears to not work under the free esxi license version:
    docker volume create –driver=store/vmware/vsphere-storage-for-docker:0.19 –name=photonv1
    Error response from daemon: create photonv1: VolumeDriver.Create: Server returned an error: (vim.fault.RestrictedVersion) {
    dynamicType = ,
    dynamicProperty = (vmodl.DynamicProperty) [],
    msg = ‘Current license or ESXi version prohibits execution of the requested operation.’,
    faultCause = ,
    faultMessage = (vmodl.LocalizableMessage) []

    Bummer. Any thoughts on making the use of the plugin and storage open as well?

  2. Keith,
    Thanks for reporting this.
    Can you please file an issue on which would be the ideal place to track it. FYI, the best mechanism to interact with Project Hatchway developers would be to follow one methods listed here – track This blog post is not monitored by the engineering team.
    Please answer following questions when you file the issue –
    1) Which ESXi version are you using? v0.19 was released in Nov 2017 and we’ve not encountered this issue from other customers.
    2) Can you reproduce this issue using the latest release (0.22)?
    3) Please upload relevant logs for debugging.


Leave a Reply

Your email address will not be published.