5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Continuing the experimentation with the Docker Volume Plugin, what I said about the iscsi initiator volume group may not always be true. My first CentOS 7 host reported the iSCSI initiator error. The error went away after I created a volume group and added the initiator name as client to that group. Secondary Docker hosts, did not seem to have this problem. I would run the "docker create volume --driver nutanix -opt sizeMB=100000 mydatavol" and it would get created and be immediately usable. It would also be visible on every docker host that I performed the 'docker volume list' command on. That is expected behavior. The learning journey continues.
Happy to report that I made it beyond various obstacles and have some small discoveries that could improve the experience a bit. One of the unfortunate bits is that the docker volume plugin does not emit much in terms of errors that will let you know what precisely went wrong. Basics: iSCSI initiator tools that you can see in Centos (iscsi-initiator-utils) and Ubuntu (open-iscsi) https://store.docker.com/plugins/nutanix-dvp-docker-volume-plug-in What those instructions do not tell you is the following. You will need to get the initiator id out of your CentOS or Ubuntu and add it to a Nutanix Volume Group as 'clients'. The Nutanix Volume Group does not have to have disks. I think this is because Nutanix needed a way to know that the VM's are allowed access to the iSCSI targets that get created through 'docker volume create' stanzas. On my system if I did not have the iqn added to a Volume Group, the docker_volume_plugin would create volumes and disks in those volumes, but t
Today I got this Docker Volume Plugin working. All the instructions out there do not warn about what to do if something goes wrong. The error from docker itself is that 'nutanix.sock' does not exist. [list=1] [*]Check your password and make sure it is updated and accurate in the command. [*]When they say default container, it means the name of the Nutanix Storage Container. It is not some volume group name or other thing. [*]You must have one volume group, named anything you want, that is configured to allow your iscsi initiator name to connect. I created one called "docker-initiators" just added the iqn to the client list. If you do not do this, then the Docker Volume Plugin will allow you to create volumes in nutanix with attached disks, but when you go to use one you'll get an error from the iSCSI initiator saying that it could not find the disk. [/list] [bjackson@localhost ~]$ docker run -it -v TestVol:/opt ubuntu /bin/bash docker: Error response from daemon: iSCSI initiat
[user=7898]aluciani[/user] Thank you for responding. We have one open #00338948. I am happy to contribute findings back to the community. The prospects of having this working are exciting.
It looks like the repository was pulled offline. Is this project still alive anywhere?
We are receiving the same error message about /run/docker/plugins/.../nutanix.sock no such file or directory. Running AOS 5.6.1 Hypervisor 20170830.124 Tried on: CentOS 7 Ubuntu 16.04 / 18.04 The docker-volume-plugin:1.1.1 is in play. Using Docker 18.03.1-ce. The Nutanix Documentation and Knowledge Base are a mess with respect to Docker because they are obviously written at different points for different audiences, pre and post 'calm.io' acquisition and include no troubleshooting guidance at all. Even the practice labs associated with calm include no information on what to do if something goes wrong. [url=http://www.nutanixworkshops.com/en/latest/calm/lab7/calm_workshop_lab7_ntnx_vol_driver_install.html]Nutanix Workshop Lab 7 - Docker Volume Plugin[/url]
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
