-
Notifications
You must be signed in to change notification settings - Fork 104
Using IdentityFile setting with docker-compose #68
Comments
I am experiencing the same issue:
Please advise. Thanks for any help! More details:
|
I moved to using a password and it seems to work well as a workaround for me. I can't touch it now because I have production stuff mounted. So if you want you can close this. I might be able to test, but not soon. |
I've been trying my hand at this, and @geoffmyers' suggestion to look at #58 did not work for me. I have tried enough times that I set up a bootstrap:
-docker plugin rm -f vieux/sshfs:latest
-sudo rm -f /var/lib/docker/plugins/sshfs-state.json
docker plugin install vieux/sshfs:latest DEBUG=1 sshkey.source=$(HOME)/.ssh/ ...and have added all conceivable debug options to the incoming:
driver: vieux/sshfs:latest
driver_opts:
sshcmd: "foo@bar:/baz"
IdentityFile: "/root/.ssh/id_rsa"
port: 2211
reconnect: ""
allow_other: ""
sshfs_debug: "" ...and {
"Description": "",
"Destination": "/root/.ssh",
"Name": "sshkey",
"Options": [
"rbind"
],
"Settable": [
"source"
],
"Source": "/home/ubuntu/.ssh/",
"Type": "bind"
} What I see in
So I'm apparently setting the key properly (since the bind mount is there), but have no real way to debug this. And yes, the key in question works, and I can do regular |
Hey,
How would I do use an IdentityFile setting with docker-compose?
I tried:
But did not seem to work
Neither did:
I get:
The text was updated successfully, but these errors were encountered: