Fork me on GitHub

ed25519 keys work fine if you use an ssh-agent


If you rely on .ssh/config you will have a bad time

Drew Verlee14:06:18

can you point to something that explains why using a config will lead to a bad time?

Drew Verlee14:06:36

This seems relevent to some of the waters i'm having to navigate.

Drew Verlee14:06:51

As i removed the config and things "just worked"

Drew Verlee14:06:04

How can i get more information about why the connector is available?

Cloning: [email protected]:Some-Repo
Error building classpath. connector is not available: 
com.jcraft.jsch.agentproxy.AgentProxyException: connector is not available: 
at com.jcraft.jsch.agentproxy.ConnectorFactory.createConnector(
In the same context i can run git clone on a repo and it succeeds.

Drew Verlee14:06:51

maybe the docker image i'm running in doesn't have something git deps expects to be installed at a system level?

Alex Miller (Clojure team)14:06:26

are you running ssh-agent?


echo $SSH_AUTH_SOCK will tell you definitively


if you're running in a docker container, probably not, unless you started it explicitly

Drew Verlee15:06:45

thanks ghadi.

Drew Verlee15:06:45

it doesn't appear to output anything. argh, ill have to somehow start it and save it between google cloud steps.

Drew Verlee15:06:52

yea. i just jump started the ssh agent first and then called clojure