Hi Megan, Thanks for taking the time to reply.
As you can see from my above config, I am configuring the SSH listen port in the startup script, and as I've also indicated, I have verified that it is also working by doing a manual SSH to the alternate port, which succeeds. So I'm confident that something _is_ listening on the other end. Is something else needed within Packer to allow this? Is there some other network/firewall type config I'm overlooking that applies to Packer, but not to direct SSH communication? Thank you, Jonathan On Friday, September 18, 2020 at 7:13:02 PM UTC+2 Megan Marsh wrote: > Packer cannot change the port that the ssh daemon is listening on in the > guest; if your startup-script isn't changing this, or it isn't being > configured elsewhere in your googlecompute configs, then it's probably > listening on the default and Packer's attempts to connect to the custom > port are in vain because no one is listening on the other end. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/cd9eb73b-259e-4427-8506-c0caf447ec72n%40googlegroups.com.
