iSharkFly-Docs/packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

detail on connecting to build VM for debugging (#3797)

Browse Source 
* detail on connecting to build VM for debugging

 - resolves #485, mostly my own confusion about how to connect to a
   locally built machine being created by packer while using -debug
   functionality.

* fixing name of preseed file typo
This commit is contained in:
Joseph Heck 2016-08-24 00:12:22 -07:00 committed by Rickard von Essen
parent 6f8ec8bd63
commit 27cdd4480a
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/source/docs/other/debugging.html.md
View File

@ -22,8 +22,13 @@ continuing. This will allow you to inspect state and so on.
In debug mode once the remote instance is instantiated, Packer will emit to the In debug mode once the remote instance is instantiated, Packer will emit to the
current directory an ephemeral private ssh key as a .pem file. Using that you current directory an ephemeral private ssh key as a .pem file. Using that you
can `ssh -i <key.pem>` into the remote build instance and see what is going on can `ssh -i <key.pem>` into the remote build instance and see what is going on
for debugging. The ephemeral key will be deleted at the end of the packer run for debugging. The key will only be emitted for cloud-based builders. The
during cleanup. ephemeral key will be deleted at the end of the packer run during cleanup.
For a local builder, the SSH session initiated will be visible in the detail
provided when `PACKER_LOG=1` environment variable is set prior to a build,
and you can connect to the local machine using the userid and password defined
in the kickstart or preseed associated with initialzing the local VM.
### Windows ### Windows