MatchbookLab / local-persist

Create named local volumes that persist in the location(s) you want
MIT License
852 stars 123 forks source link

cannot remove local-persist volume #66

Closed kspoon01 closed 4 years ago

kspoon01 commented 5 years ago

docker volume rm etfdb_pgdata Error response from daemon: get etfdb_pgdata: error while checking if volume "etfdb_pgdata" exists in driver "local-persist": Post http://%2Frun%2Fdocker%2Fplugins%2Flocal-persist.sock/VolumeDriver.Get: dial unix /run/docker/plugins/local-persist.sock: connect: connection refused

docker version is 18.09.0, build 4d60db4

I am pretty new to docker, please let me know what else I should provide.

Why is it trying to access the web?

devopsn commented 5 years ago

I met with the same problem, restarting the docker helped me.

datocrats-org commented 4 years ago

Related concern, if for any reason in the future developers were told to no longer use local-persist as a driver in docker-compose for example, how would you recommend migrating back to named volumes using another "driver"? Is that possible?

CWSpear commented 4 years ago

@datocrats-org You just move the actual data wherever that other driver supports... nothing magic or special here.

CWSpear commented 4 years ago

@kspoon01 you've definitely move on from here, but it's trying to access the socket, which is how it communicates. Maybe something was configured wrong that you had it looking at the wrong address or something.

taeun0 commented 2 years ago

I have a same issue. I am trying to run local-persist and occurs same meesage. Is there anyone solved this problem? Is it occurs because volume name already exists? I tried this.

$ docker volume create -d local-persist -o mountpoint=/{path} mongo-configsvr-data
Error response from daemon: create mongo-configsvr-data: found reference to volume 'mongo-configsvr-data' in driver 'local-persist', but got an error while checking the driver: error while checking if volume "mongo-configsvr-data" exists in driver "local-persist": Post http://%2Frun%2Fdocker%2Fplugins%2Flocal-persist.sock/VolumeDriver.Get: dial unix /run/docker/plugins/local-persist.sock: connect: connection refused: volume name must be unique

$ docker volume ls
DRIVER              VOLUME NAME
local-persist       mongo-configsvr-data
taeun0 commented 2 years ago

I have a same issue. I am trying to run local-persist and occurs same meesage. Is there anyone solved this problem? Is it occurs because volume name already exists? I tried this.

$ docker volume create -d local-persist -o mountpoint=/{path} mongo-configsvr-data
Error response from daemon: create mongo-configsvr-data: found reference to volume 'mongo-configsvr-data' in driver 'local-persist', but got an error while checking the driver: error while checking if volume "mongo-configsvr-data" exists in driver "local-persist": Post http://%2Frun%2Fdocker%2Fplugins%2Flocal-persist.sock/VolumeDriver.Get: dial unix /run/docker/plugins/local-persist.sock: connect: connection refused: volume name must be unique

$ docker volume ls
DRIVER              VOLUME NAME
local-persist       mongo-configsvr-data

In my case, we solved it by restarting docker process. Maybe it seems to be a docker problem...😓

CWSpear commented 2 years ago

It seems to say you're trying to create a volume that already exists. You can delete the volume (which will not delete the underlying data if you've got it pointing to a folder elsewhere on your drive).

Depending on all what you did, restarting probably worked cuz it removed the volume.

On Tue, Aug 30, 2022, 4:43 PM taeun @.***> wrote:

I have a same issue. I am trying to run local-persist and occurs same meesage. Is there anyone solved this problem? Is it occurs because volume name already exists? I tried this.

$ docker volume create -d local-persist -o mountpoint=/{path} mongo-configsvr-data

Error response from daemon: create mongo-configsvr-data: found reference to volume 'mongo-configsvr-data' in driver 'local-persist', but got an error while checking the driver: error while checking if volume "mongo-configsvr-data" exists in driver "local-persist": Post http://%2Frun%2Fdocker%2Fplugins%2Flocal-persist.sock/VolumeDriver.Get: dial unix /run/docker/plugins/local-persist.sock: connect: connection refused: volume name must be unique

$ docker volume ls

DRIVER VOLUME NAME

local-persist mongo-configsvr-data

In my case, we solved it by restarting docker process. Maybe it seems to be a docker problem...😓

— Reply to this email directly, view it on GitHub https://github.com/MatchbookLab/local-persist/issues/66#issuecomment-1232281603, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADZB34IAJL2JWHXFMAFGQDV32MAZANCNFSM4GIDFZBQ . You are receiving this because you modified the open/close state.Message ID: @.***>

taeun0 commented 2 years ago

thank you for reply!

andycarlberg commented 2 years ago

Sorry to hit such an old issue but it's the only reference to my problem I've been able to find.

I'm getting this error when trying to create a new volume with the local-persist driver.

Error response from daemon: create new_volume: error looking up volume plugin local-persist: legacy plugin: Post "http://%2Frun%2Fdocker%2Fplugins%2Flocal-persist.sock/Plugin.Activate": dial unix /run/docker/plugins/local-persist.sock: connect: connection refused

I can't find much info on this issue or how to resolve it. The volume doesn't exist yet. This is what I get on initial creation.