You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
Some of our environments run ssh commands (e.g. git clone with an ssh path) that are reliant on key forwarding. When the host doesn't have any keys loaded (check ssh-add -l), no keys are forwarded to the VM and these operations fail -- whereas if they were run on the host, the keys would be transparently loaded at that point.
Could we use a trigger to run ssh-add on vagrant up? And maybe only run it if ssh-add -l is empty?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Some of our environments run ssh commands (e.g. git clone with an ssh path) that are reliant on key forwarding. When the host doesn't have any keys loaded (check
ssh-add -l
), no keys are forwarded to the VM and these operations fail -- whereas if they were run on the host, the keys would be transparently loaded at that point.Could we use a trigger to run
ssh-add
onvagrant up
? And maybe only run it ifssh-add -l
is empty?The text was updated successfully, but these errors were encountered: