5093f3120e
This is a big commit, and I apologize in advance for the future
git-blames all pointing to me. This commit does a few things:
1. Merges the website/docs and website/www repo into a single website repo
to be in line with other HashiCorp projects
2. Updates to use middleman-hashicorp
3. Converts less to scss to be in line with other projects
4. Updates page styles to be in line with other projects
5. Optimizes images
6. Prepare for S3 + Fastly deployment with scripts, etc.
7. Removes blog posts (they have been transferred to hashicorp.com with
redirects in place
8. Updated sitemap generation script for better SEO
9. Fixed many broken links
10. Add description to all fields
1.3 KiB
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| docs | vagrant ssh - Command-Line Interface | cli-ssh | The "vagrant ssh" command is used to establish an SSH session into a running virtual machine to give you shell access. |
SSH
Command: vagrant ssh
This will SSH into a running Vagrant machine and give you access to a shell.
If a -- (two hyphens) are found on the command line, any arguments after
this are passed directly into the ssh executable. This allows you to pass
any arbitrary commands to do things such as reverse tunneling down into the
ssh program.
Options
-
-c COMMANDor--command COMMAND- This executes a single SSH command, prints out the stdout and stderr, and exits. -
-por--plain- This does an SSH without authentication, leaving authentication up to the user.
Background Execution
If the command you specify runs in the background (such as appending a & to
a shell command), it will be terminated almost immediately. This is because
when Vagrant executes the command, it executes it within the context of a
shell, and when the shell exits, all of the child processes also exit.
To avoid this, you will need to detach the process from the shell. Please
Google to learn how to do this for your shell. One method of doing this is
the nohup command.