Timeline for How to ssh to vagrant without actually running "vagrant ssh"?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 11, 2022 at 12:09 | comment | added | Chris | Great answer. Super easy. The only problem I had was my encoding was wrong. But a simple here took care of the problem. stackoverflow.com/questions/55693854/… | |
| Aug 3, 2019 at 2:04 | comment | added | abulka |
By adding an entry to the ~/.ssh/config in the way @adamczi suggests you can then use the Visual Studio Code Remote - SSH extension to ssh into the Vagrant VM and edit files and do remote development. Simply CMD-SHIFT-P then "Remote-SSH: Connect to Host..." and the ssh .config entry you just added is automatically listed - you simply select it and voila, vscode connects to your remote vagrant vm! Without the config entry approach, I'm not sure how else I would have done it with vscode.
|
|
| Feb 2, 2019 at 16:33 | comment | added | laimison |
Thanks @adamczi this is the simplified way which also works for automated solutions where adding extra ssh parameter -F is not straightforward
|
|
| Sep 4, 2018 at 19:32 | comment | added | adamczi |
You might want echo this result into your ssh config file: vagrant ssh-config >> ~/.ssh/config , so you just run ssh default from anywhere in your system, where default is the name of the VM that you can specify like here
|
|
| Aug 30, 2017 at 16:17 | comment | added | liori |
With some shells (e.g. zsh), the following one-liner works: ssh -F =(vagrant ssh-config) default
|
|
| May 2, 2017 at 15:33 | comment | added | sashaegorov |
That is amazing. Mind adding vagrant-ssh file in .gitignore.
|
|
| Apr 8, 2017 at 20:53 | review | Suggested edits | |||
| Apr 9, 2017 at 6:07 | |||||
| May 15, 2014 at 17:58 | history | answered | Steven Soroka | CC BY-SA 3.0 |