-
Notifications
You must be signed in to change notification settings - Fork 95
CoreOS - vsphere.socket not found #1924
Comments
@mlabouardy can you please share docker service logs? |
@mlabouardy, also can you check and upload /var/log/docker-volume-vsphere.log if one is present in the coreOS host. |
@govint
|
Seems to be related to a coreOS specific issue - docker/go-plugins-helpers#38, the socket file vsphere.sock possibly needs to be created with group as docker vs. root. The plugin is creating the socket with group as root and that seems to be causing the issue here. Lets check that setting the group as docker works fine with any host. Consider also making this a config option with a default as root. Docker seems to use group ID as docker anyway, |
I'm planning on adding a config option to specify the GID of the socket file with the default as root. The GID of docker is what docker uses and should work ok (will check on coreOS). |
Fixes are in place and will complete the testing and get this out for a review. |
I did stumble upon the same error today, which led me to this issue. Then, i had to look around your docs quite a bit to find the config option you mentioned. The command which worked for me on CoreOS was: docker plugin install --grant-all-permissions --alias vsphere vmware/vsphere-storage-for-docker:latest "VDVS_SOCKET_GID=223" Maybe you can put some information on this into the documentation, in the part where the installation is described. |
I cannot install vsphere plugin on CoreOS machine with docker 17.06
Docker version:
CoreOS version:
The text was updated successfully, but these errors were encountered: