This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
Added dependency to vm tools [SKIP CI] #1750
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shaominchen
approved these changes
Aug 14, 2017
README.md
Outdated
| @@ -157,11 +157,16 @@ logging config format for content details. | |||
|
|
|||
| **Docker**: 1.12 and higher (Recommended 1.13/17.03 and above to use managed plugin) | |||
|
|
|||
| # Dependencies | |||
|
|
|||
| The plugin uses VMCI (Virtual Machine Communication Interface) and VSockets to contact the service on ESX. The associated Linux kernel drivers are installed via the VMware Tools and its open version, namely [open-vm-tools](https://github.com/vmware/open-vm-tools), packages. Either one of these packages must hence be installed in the guest OS. Its recommended to install the most uptodate version of either of these packages as available. | |||
There was a problem hiding this comment.
Nits:
- VSockets => vSockets
- Its recommended => It's recommended
README.md
Outdated
| # Known Issues | ||
|
|
||
| - Volume metadata file got deleted while removing volume from VM(placed on Esx2) which is in use by another VM(placed on Esx1) [#1191](https://github.com/vmware/docker-volume-vsphere/issues/1191). It's an ESX issue and will be available in the next vSphere release. | ||
| - Full volume name with format like "volume@datastore" cannot be specified in the compose file for stack deployment. [#1315](https://github.com/vmware/docker-volume-vsphere/issues/1315). It is a docker compose issue and a workaround has been provided in the issue. | ||
| - Volume creation using VFAT filesystem is not working currently. [#1327](https://github.com/vmware/docker-volume-vsphere/issues/1327) | ||
| - Plugin fails to create volumes after installation on VM running boot2docker Linux. This is because open-vm-tools available for boot2docker doesn't install the vsockets driver and hence the plugin is unable to contact the ESX service. [#1744](https://github.com/vmware/docker-volume-vsphere/issues/1744) |
There was a problem hiding this comment.
Nit: vsockets => vSockets
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a note on the dependency on vm-tools for the plugin.