Closed divyenpatel closed 6 years ago
Correctness
[x] http://vmware.github.io/docker-volume-vsphere/documentation/docker-volume-cli.html mentions ’The docker volume commands are completely supported by vDVS plugin.’ and in the same page it is mentioned that prune volume command is not supported.
[x] http://vmware.github.io/docker-volume-vsphere/documentation/docker-volume-cli.html has link Storage policy based management that takes user to this page http://vmware.github.io/policy-based-management.html, which doesn’t really show any details about policy based management.
[x] http://vmware.github.io/docker-volume-vsphere/documentation/tenancy.html#admin-cli has link for ‘Design Spec for tenancy’ that leads to 404 https://github.com/vmware/docker-volume-vsphere/blob/master/docs/misc/docker-volume-auth-proposal.v1_2.md. The link doesn’t seem useful for documentation.
Typos & formatting
Usage
[x] From documentation it’s not clear that once created, vmgroup’s volume-maxsize and volume-totalsize can be updated later or not. If update is allowed what will happen to the existing volumes that doesn’t match those new restrictions.
[x] One simple example of for creating container with volume would be useful. None of the current examples demonstrate this usage: docker run -it --volume-driver=vsphere -v MyVolume@sharedVmfs-0:/vol1 --name ub ubuntu. Existing examples make use of docker compose only.
PR is merged. vDVS documentation is updated. Thanks @prashima and @divyenpatel.
[ @ashahi1 ] It is already documented at http://vmware.github.io/docker-volume-vsphere/documentation/faq.html#can-i-migrate-data-between-linux-and-windows-containers
[ @shuklanirdesh82 ] It was fixed through https://github.com/vmware/docker-volume-vsphere/pull/2011