Hi,

I have a Packer (v. 0.11.0) build that outputs a VirtualBox (v. 5.0.24_Ubuntu 
r108355) VM that I then want Packer to make Vagrant (v 1.8.7) friendly. I 
have my Vagrant post-processor configured to leave the VirtualBox working 
files:

  "post-processors": [
    {
      "output": "builds/{{.Provider}}-centos6.box",
      "type": "vagrant",
      "keep_input_artifact": true
    }
  ]

I'm wanting to use the insecure SSH key but when I try to `vagrant up` on 
the finished product the key authentication fails. Looking at the 
~/.ssh/authorized_keys files I see they are different between the vmdk 
that's bundled up in the final .box versus the vmdk working file. The 
working files vmdk's authorized_keys file has the public key that I've 
downloaded and configured as a part of my provisioning, but after the 
Vagrant post-processor runs, the key in authorized_keys has been changed. 
I've tried setting the config.ssh.private_key_path in my Vagrantfile to my 
personal private key and the private key 
at ~/.vagrant.d/insecure_private_key but neither seems to correspond to key 
in the vagrant output (or at least I get an authentication failure when I 
try to vagrant up).

I want to use the insecure SSH in the vagrant box but I don't see an option 
in the vagrant post-processor to not do whatever it's doing to rewrite the 
value in the authorized_keys file. Any tips?

Thanks,
Kevin

-- 
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/mitchellh/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/267c96fe-4ed3-4a70-8549-a7bdd71e7a78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to