New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fallback to ~/.ssh during docker profile creation #150

Closed
cburroughs opened this Issue Dec 13, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@cburroughs
Contributor

cburroughs commented Dec 13, 2016

Followup to #108

When we find a key fingerprint in both ~/.ssh and ssh-agent we prefer the one in the agent. This is basically the expectation of using an agent to begin with (no repeat password entry), but when creating the docker cert the local triton command needs the private key. The agent can't/won't provide a private key and we currently fail with something along the lines of:

triton profile docker-setup: error (Setup): could not obtain SSH private key for keypair with fingerprint 

In the common case of working on a local workstation (no agent forwarding) we could "fallback" to trying to read out of ~/.ssh.

@trentm

This comment has been minimized.

Show comment
Hide comment
@trentm
Member

trentm commented Feb 21, 2017

joyent-automation pushed a commit that referenced this issue Feb 21, 2017

#150 fallback to ~/.ssh during docker profile creation
Reviewed by: Todd Whiteman <todd.whiteman@joyent.com>
Approved by: Todd Whiteman <todd.whiteman@joyent.com>

@trentm trentm closed this Feb 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment