From 27cdd4480a5a0349683fe5716729000bfb1bb9ad Mon Sep 17 00:00:00 2001 From: Joseph Heck Date: Wed, 24 Aug 2016 00:12:22 -0700 Subject: [PATCH] detail on connecting to build VM for debugging (#3797) * 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 --- website/source/docs/other/debugging.html.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/website/source/docs/other/debugging.html.md b/website/source/docs/other/debugging.html.md index d238fe7ca..62313d07e 100644 --- a/website/source/docs/other/debugging.html.md +++ b/website/source/docs/other/debugging.html.md @@ -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 current directory an ephemeral private ssh key as a .pem file. Using that you can `ssh -i ` 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 -during cleanup. +for debugging. The key will only be emitted for cloud-based builders. The +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