###前提・実現したいこと
同僚からboxを渡されてVagrantfileを全くいじらない状態だとvagrant up後, vagrant ssh可能なのですが、vagrantfileに以下の設定を追記すると、エラーが出ます。
config.vm.network "private_network", ip: "192.168.33.10" または config.vm.network "forwarded_port", guest: 80, host: 8080
###発生している問題・エラーメッセージ
vagrant up後
==> default: Configuring and enabling network interfaces... The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! # Down the interface before munging the config file. This might # fail if the interface is not actually set up yet so ignore # errors. /sbin/ifdown 'eth1' # Move new config into place mv -f '/tmp/vagrant-network-entry-eth1-1482227070-0' '/etc/sysconfig/network-scripts/ifcfg-eth1' # attempt to force network manager to reload configurations nmcli c reload || true # Restart network (through NetworkManager if running) if service NetworkManager status 2>&1 | grep -q running; then service NetworkManager restart else service network restart fi Stdout from the command: Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0... done. [ OK ] Bringing up interface eth1: Determining if ip address 192.168.33.20 is already in use for device eth1... [ OK ] Bringing up interface eth2: Device eth2 does not seem to be present, delaying initialization. [FAILED] Stderr from the command: bash: line 10: nmcli: command not found
###補足情報(言語/FW/ツール等のバージョンなど)
virtualbox 5.0.14
vagrant 1.9.1
バッドをするには、ログインかつ
こちらの条件を満たす必要があります。