Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

Project discontinued? #2091

Open
raptaml opened this issue Sep 18, 2018 · 5 comments
Open

Project discontinued? #2091

raptaml opened this issue Sep 18, 2018 · 5 comments

Comments

@raptaml
Copy link

raptaml commented Sep 18, 2018

Hello,
I have seen no progress on this for several month, is it discontinued? We planned to use this in production, are there any alternatives or will it get picked up again?

Thanks

@anthonyloukinas
Copy link

Would also like to know the status of this project. Most of the issues still open have been open for months with no end in sight.

A specific issue we are facing is the expansion of volumes after they've been provisioned. StorageOS and other volume drivers are handling this fine, but the VMWare Storage For Docker team has closed out all of the old issues relating to this.
#1876

@nartamonov
Copy link

+1 what's the status of this project?

@vkolli01
Copy link

vkolli01 commented Mar 7, 2019

There is no active development happening for this driver, nor is planned in the near future. We have shifted our efforts to Kubernetes solutions.
Volume expansion support is being planned for kubernetes driver.

@aleskinen
Copy link

aleskinen commented May 13, 2019

Should this be compatible vith vmware 6.7?
We recently updated to 6.7 now I get errors like
May 13 09:28:45 dca dockerd[336]: time="2019-05-13T09:28:45.361945009Z" level=error msg="fatal task error" error="VolumeDriver.Mount: Device not found" module="node/agent/taskmanager" node.id=pd9mvqohram9ewygqyyjiui27 service.id=7t1obs5rmin23hpvcgdb0nyq3 task.id=m7qsr5x0z05viyqqnu3nnig7q
Still docker volume info returns correct info.

@jostmart
Copy link

So there is actually no good solution for Docker Swarm users if this project is scrapped.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants