You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
VI Admins can create VSAN policies which then are consumed by end users (Developers) when creating the Docker Volumes. However, it doesn't look like Docker can query the plugin capabilities today which would mean the VI Admin must then communicate this info to all the Developers which isn't really a scalable solution.
The text was updated successfully, but these errors were encountered:
As a poor man solution, and given Docker is missing any APIs for communicating extra info,
I suggest to report list of avail policies on command line failure: docker volume create --driver=vmdk --name=doesnotmatter -o policy=some-bad-name
and we'll reply with Error: no such policy: some-bad-name. Available policies are : <list...>
VI Admins can create VSAN policies which then are consumed by end users (Developers) when creating the Docker Volumes. However, it doesn't look like Docker can query the plugin capabilities today which would mean the VI Admin must then communicate this info to all the Developers which isn't really a scalable solution.
The text was updated successfully, but these errors were encountered: