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/CAGPV1uqHfSBTcZY801QN6Zjzv%2BVcCfdKwVCP3BWUL5S1Ly3ucA%40mail.gmail.com.
