SSH Proxy?

[Timothy Perrett]

Hey guys,

When packer is trying to verify that an instance was created, will it honour the SSH proxy configuration on the machine? Namely, ~/.ssh/config ? Packer is working beautifully on our external network, but on the private build network that is more restricted it fails, which i believe to be because of the proxy.

Any help greatly appreciated. 

Thanks, Tim 

[Jack Pearkes]

Tim,

There's currently an open issue for SSH proxy support: https://github.com/mitchellh/packer/issues/387

Packer will not honor your SSH configuration as it implements it internally: https://github.com/mitchellh/packer/tree/master/communicator/ssh

Hope that helps!

Best,

Jack

--
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 packer-tool...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Timothy Perrett]

Thanks for the reply Jack, but my reaction was pretty much "noooooo!". 

This really is a shame - corporate networks are a pain, that is for sure. Packer does everything we want, this is the only fly in the ointment as it wont run on the build servers on the corpnet :-( Can you think of any possible work arounds?

Do you feel like it would be a hard feature to implement? I'm a functional programmer by trade, and don't know go, unfortunately, otherwise i'd send a pull request myself. 

Cheers, Tim 

[Bill WANG]

Now the solution is ready. Set ssh communicator to access aws via jumphost (bastion box).

https://packer.io/docs/templates/communicator.html

Sample for reference.:

https://www.hashicorp.com/blog/packer-0-8.html

    "builders": [{
        ...,
        "communicator": "ssh",
        "ssh_bastion_host": "1.2.3.4",
        "ssh_bastion_username": "foo",
        "ssh_bastion_private_key_file": "{{template_dir}}/bastion.key"
    }],