4

I'm using a bridged network on a vagrant VM with chef-client. knife node show test1-vagrant shows an ip address of 10.0.2.15, which is eth0. eth1 is 192.168.1.5, which is what DHCP gave it. How can i get chef thinking the ip address is 192.168.1.5 instead, so that I can knife ssh -a ipaddress?

  • Consider running your VirtualBox VMs in bridged mode instead of NAT mode. – Michael Hampton Nov 7 '12 at 1:34
  • Even though you have private/public network configured Chef provisioner still uses 10.0.2.15 as node['ipaddress'] – Maxim Vladimirsky Apr 25 '13 at 8:05
  • maybe this is the ticket on the opscode site? – cwd Aug 13 '14 at 1:14
3

This cookbook might help you, it changes the ipaddress node attribute to use the ip address associated to the eth1 interface: https://github.com/tknerr/cookbooks-vagrant-ohai

2

Here is a complete Vagrant Plugin that installs an ohai plugin that does something similar https://github.com/avishai-ish-shalom/vagrant-ohai

Only problem is right now it seems to only install it if you are using the :chef_solo or :chef_server provisioner.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.