-
Notifications
You must be signed in to change notification settings - Fork 103
Error response from daemon: VolumeDriver.Mount: exit status 1%!(EXTRA []interface {}=[]). #45
Comments
Maybe it caused by the remote path is not exists. Try to create the remote path first, then mount the volume. |
I already double checked that both the remote and locks dirs exist.
On Jan 5, 2018 3:14 AM, "Athurg Feng" <notifications@github.com> wrote:
Maybe it caused by the remote path is not exists.
Try to create the remote path first, then mount the volume.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD5_bWRnKM7921wi_wG37eX39XKhajoyks5tHdnSgaJpZM4RSGl1>
.
|
@swvajanyatek - did you get this figured out? I am having exactly the same error. I am also new to this plugin and docker. |
@jfinlins - unfortunately, no. i moved forward with sshfs from inside the container. |
the same issue. |
Getting the same issue |
seems like plugin doesn't work...((( |
@swvajanyatek, try changing You can also update your settings to automatically include you key by running I just started playing around with |
Same issue here. Using sshfs inside container works with |
docker run -it -v sshvolume:/tmp busybox pwd Same issue ( |
I have the same issue here : run on latest debian |
Same here with Docker version 18.02.0-ce, build fc4de44 |
Same problem here with 17.12.1-ce. |
Same issue for me with Docker version 17.12.1-ce, build 7390fc6 |
Same here (17.04.0-ce, build 4845c56). Any solutions or at least ideas how to debug this? |
Found a solution:
|
To me it was a problem of understanding the needed paths correctly. I could clarify this thanks to #58, but only partially:
I think this should be clarified in the README. |
I see:
if I use key from non-root user. Docker run volume plugin from root and
Solution (work for me)
|
|
@houxiyao try to check ssh connection from root to destination without docker sshfs plugin (try to only connect by ssh) |
also check config |
Seems there is bug in vieux/sshfs volume driver plugin.
$ docker volume ls (worker node)
Is there any way to look around to solve ....? please suggest |
I've added single quotes and it worked
|
Found this that can potentially be helpful ... Look at : #19 (comment) |
I'm able to create the volume successfully, but when I try to utilize it, I get the following error:
create:
this is my first foray into vieux/sshfs, so I'm not entierly sure this is a bug.
The text was updated successfully, but these errors were encountered: