Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- $ kitchen create default-ubuntu-1604
- -----> Starting Kitchen (v1.13.2)
- -----> Creating <default-ubuntu-1604>...
- Bringing machine 'default' up with 'virtualbox' provider...
- ==> default: You assigned a static IP ending in ".1" to this machine.
- ==> default: This is very often used by the router and can cause the
- ==> default: network to not work properly. If the network doesn't work
- ==> default: properly, try changing this IP.
- ==> default: Importing base box 'bento/ubuntu-16.04'...
- ==> default: Matching MAC address for NAT networking...
- ==> default: You assigned a static IP ending in ".1" to this machine.
- ==> default: This is very often used by the router and can cause the
- ==> default: network to not work properly. If the network doesn't work
- ==> default: properly, try changing this IP.
- ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
- ==> default: A newer version of the box 'bento/ubuntu-16.04' is available! You currently
- ==> default: have version '2.3.0'. The latest is version '2.3.1'. Run
- ==> default: `vagrant box update` to update.
- ==> default: Setting the name of the VM: kitchen-hwk-default-ubuntu-1604_default_1480787084932_41047
- Vagrant cannot forward the specified ports on this VM, since they
- would collide with some other application that is already listening
- on these ports. The forwarded port to 8123 is already in use
- on the host machine.
- To fix this, modify your current project's Vagrantfile to use another
- port. Example, where '1234' would be replaced by a unique host port:
- config.vm.network :forwarded_port, guest: 80, host: 1234
- Sometimes, Vagrant will attempt to auto-correct this for you. In this
- case, Vagrant was unable to. This is usually because the guest machine
- is in a state which doesn't allow modifying port forwarding. You could
- try 'vagrant reload' (equivalent of running a halt followed by an up)
- so vagrant can attempt to auto-correct this upon booting. Be warned
- that any unsaved work might be lost.
- >>>>>> ------Exception-------
- >>>>>> Class: Kitchen::ActionFailed
- >>>>>> Message: 1 actions failed.
- >>>>>> Failed to complete #create action: [Expected process to exit with [0], but received '1'
- ---- Begin output of vagrant up --no-provision --provider virtualbox ----
- STDOUT: Bringing machine 'default' up with 'virtualbox' provider...
- ==> default: You assigned a static IP ending in ".1" to this machine.
- ==> default: This is very often used by the router and can cause the
- ==> default: network to not work properly. If the network doesn't work
- ==> default: properly, try changing this IP.
- ==> default: Importing base box 'bento/ubuntu-16.04'...
- ==> default: Matching MAC address for NAT networking...
- ==> default: You assigned a static IP ending in ".1" to this machine.
- ==> default: This is very often used by the router and can cause the
- ==> default: network to not work properly. If the network doesn't work
- ==> default: properly, try changing this IP.
- ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
- ==> default: A newer version of the box 'bento/ubuntu-16.04' is available! You currently
- ==> default: have version '2.3.0'. The latest is version '2.3.1'. Run
- ==> default: `vagrant box update` to update.
- ==> default: Setting the name of the VM: kitchen-hwk-default-ubuntu-1604_default_1480787084932_41047
- STDERR: Vagrant cannot forward the specified ports on this VM, since they
- would collide with some other application that is already listening
- on these ports. The forwarded port to 8123 is already in use
- on the host machine.
- To fix this, modify your current project's Vagrantfile to use another
- port. Example, where '1234' would be replaced by a unique host port:
- config.vm.network :forwarded_port, guest: 80, host: 1234
- Sometimes, Vagrant will attempt to auto-correct this for you. In this
- case, Vagrant was unable to. This is usually because the guest machine
- is in a state which doesn't allow modifying port forwarding. You could
- try 'vagrant reload' (equivalent of running a halt followed by an up)
- so vagrant can attempt to auto-correct this upon booting. Be warned
- that any unsaved work might be lost.
- ---- End output of vagrant up --no-provision --provider virtualbox ----
- Ran vagrant up --no-provision --provider virtualbox returned 1] on default-ubuntu-1604
- >>>>>> ----------------------
- >>>>>> Please see .kitchen/logs/kitchen.log for more details
- >>>>>> Also try running `kitchen diagnose --all` for configuration
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement