Join us for the next global Nutanix User Group webinar where we'll discuss the <\/span>Top 3 Ways to Build Cyber Resilience Against Ransomware<\/strong><\/span> with Nutanix with Mike Barmonde, Nutanix Sr. Product Marketing Manager, and Neil Ashworth, Nutanix Portfolio Architect.<\/span><\/p>

Here\u2019s what will be covered:\u00a0<\/p>

  • Insights into ransomware evolution<\/span><\/li>\t
  • What is cyber resilience and how it fights ransomware\u00a0<\/span><\/li>\t
  • Demos on 3 key Nutanix concepts that will help you build cyber resilience<\/span><\/li><\/ul>

    Register today!\u00a0<\/span><\/p>","author":{"id":113632,"url":"\/members\/karlie-beil-113632","name":"Karlie Beil","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/1581aab3-bcf6-49f4-b2fb-3d11e8c010dc.png","userTitle":"Community Manager","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Community Manager","color":"#0873ba"},"userLevel":5},"type":"Meetup","url":"https:\/\/next.nutanix.com\/events\/global-nug-top-3-ways-to-build-cyber-resilience-176","image":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/050d4c6e-b652-40ce-9988-03189c05e3b9_thumb.png","location":"","startsAt":1686841200,"endsAt":1686844800,"contentType":"event","attendees":[],"attendeeCount":0,"isLoggedInUserAttendee":false,"createdAt":"1684788278"},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

Nutanix DVP (Docker Volume Plug-in)

  • 24 November 2017
  • 4 replies
  • 1629 views
阿卢西亚尼
Userlevel 7
Badge +34
Earlier in the year we shared our Nutanix Docker Volume Plugin on the Docker store. The Nutanix Docker Volume Plugin (DVP) enables Docker Containers to use storage persistently. Normally, if a container is moved from one container machine to another, storage does not move with it.

The Acropolis Container Services (ACS) provide a storage volume plugin that enables Docker deployments to be integrated with Nutanix external storage systems and enable data volumes to persist beyond the lifetime of a single container machine host.

You can find it here:Nutanix DVP (Docker Volume Plug-in)

命中答复并与社区中的其他人分享您的经验！
\n
\nThe Acropolis Container Services (ACS) provide a storage volume plugin that enables Docker deployments to be integrated with Nutanix external storage systems and enable data volumes to persist beyond the lifetime of a single container machine host.
\n
\nYou can find it here: Nutanix DVP (Docker Volume Plug-in)<\/a>
\n
\nHit REPLY and share your experience with others in the community!","quoteUsername":"aluciani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
This topic has been closed for comments

4 replies

M
Badge
您是否需要在Nutanix节点上运行ACS来使用ACS？这个插件可以与正在运行VMware NSX而不是Acripolis的节点一起使用吗？
阿卢西亚尼
Userlevel 7
Badge +34
MP3写道：您需要在Nutanix节点上运行ACS以使用ACS吗？这个插件可以与正在运行VMware NSX而不是Acripolis的节点一起使用吗？

Himp3I suspect you meant ESXi in the above comment - If so then yes it will work with nodes running ESXi.
mp3 wrote:Do you need to be running Acropolis on your Nutanix Nodes to use ACS? Could this plugin work with Nodes that are running VMware NSX instead of Acropolis?
\n<\/blockquote>
\nHi mp3<\/a> I suspect you meant ESXi in the above comment - If so then yes it will work with nodes running ESXi.","quoteUsername":"aluciani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
S
Badge
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.

  1. 检查您的密码，并确保在命令中对其进行更新和准确。
  2. When they say default container, it means the name of the Nutanix Storage Container. It is not some volume group name or other thing.
  3. 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.
[bjackson@localhost〜] $ docker run -it -v testvol：/opt ubuntu/bin/bash
Docker：守护程序的错误响应：ISCSI发起者错误：无法在主机上找到磁盘。

Example command to get the plugin installed:
docker plugin install ntnx/nutanix_volume_plugin:latest PRISM_IP="172.30.0.50" DATASERVICES_IP="172.30.3.9" PRISM_PASSWORD="Nutanix/4u&" PRISM_USERNAME="bjackson" DEFAULT_CONTAINER="BI_Storage" --alias nutanix

The PRISM_IP is obvious. The DATASERVICES_IP, the existing documents make sound super complicated and special. In the cluster details within Prism, you just make up an IP that exists within your subnet (IP Range) that is free and you want to use for all VM's that use iSCSI pointed back at the Nutanix Cluster, and that is it. If you change it later, you will probably have to remove and reinstall the docker volume plugin again with the updated IP address.

如果您删除了“ -alias nutanix”，则必须使用驱动程序的丑陋全名来引用它（例如：ntnx/nutanix_volume_plugin：1.1.1或其他一些标签名称）。

Not sure if it is possible to update the existing plugin once it is installed. So far, I had to do 'docker plugin rm nutanix', then rerun the above command for installing it in the first place. Success means you don't get any messages back beyond asking for permission for the plugin to access various things.

Absolutely nothing is documented about these. One password change and things could randomly go south with your containers and attached volumes. Hope this helps someone over the hill.
\r\n
\r\n
    \r\n
  1. Check your password and make sure it is updated and accurate in the command. \r\n
  2. When they say default container, it means the name of the Nutanix Storage Container. It is not some volume group name or other thing. \r\n
  3. 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. \r\n<\/ol>\r\n[bjackson@localhost ~]$ docker run -it -v TestVol:\/opt ubuntu \/bin\/bash
    \r\ndocker: Error response from daemon: iSCSI initiator error: Could not find disk on host.
    \r\n
    \r\nExample command to get the plugin installed:
    \r\ndocker plugin install ntnx\/nutanix_volume_plugin:latest PRISM_IP=\"172.30.0.50\" DATASERVICES_IP=\"172.30.3.9\" PRISM_PASSWORD=\"Nutanix\/4u&\" PRISM_USERNAME=\"bjackson\" DEFAULT_CONTAINER=\"BI_Storage\" --alias nutanix
    \r\n
    \r\nThe PRISM_IP is obvious. The DATASERVICES_IP, the existing documents make sound super complicated and special. In the cluster details within Prism, you just make up an IP that exists within your subnet (IP Range) that is free and you want to use for all VM's that use iSCSI pointed back at the Nutanix Cluster, and that is it. If you change it later, you will probably have to remove and reinstall the docker volume plugin again with the updated IP address.
    \r\n
    \r\nIf you leave off the '--alias nutanix', you'll have to use the ugly full name of the driver to reference it (ex: ntnx\/nutanix_volume_plugin:1.1.1 or some other tag name).
    \r\n
    \r\nNot sure if it is possible to update the existing plugin once it is installed. So far, I had to do 'docker plugin rm nutanix', then rerun the above command for installing it in the first place. Success means you don't get any messages back beyond asking for permission for the plugin to access various things.
    \r\n
    \r\nAbsolutely nothing is documented about these. One password change and things could randomly go south with your containers and attached volumes. Hope this helps someone over the hill.","quoteUsername":"smoodo","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
S
Badge
使用Docker卷插件继续实验，我对ISCSI启动器量组的说法可能并不总是正确的。我的第一个CentOS 7主机报告了ISCSI启动器错误。在我创建一个卷组并将启动器名称作为客户端添加到该组之后，该错误消失了。次要Docker主持人似乎没有这个问题。我将运行“ Docker Create卷-Driver Nutanix -opt Sizemb = 100000 mydatavol”，它将被创建并立即使用。在我执行“ Docker卷列表”命令的每个Docker主机上也可以看到它。那是预期的行为。学习旅程继续。
条款和条件
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu