Advertisement
Guest User

Untitled

a guest
Dec 3rd, 2016
59
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.52 KB | None | 0 0
  1. $ kitchen create default-ubuntu-1604
  2. -----> Starting Kitchen (v1.13.2)
  3. -----> Creating <default-ubuntu-1604>...
  4. Bringing machine 'default' up with 'virtualbox' provider...
  5. ==> default: You assigned a static IP ending in ".1" to this machine.
  6. ==> default: This is very often used by the router and can cause the
  7. ==> default: network to not work properly. If the network doesn't work
  8. ==> default: properly, try changing this IP.
  9. ==> default: Importing base box 'bento/ubuntu-16.04'...
  10. ==> default: Matching MAC address for NAT networking...
  11. ==> default: You assigned a static IP ending in ".1" to this machine.
  12. ==> default: This is very often used by the router and can cause the
  13. ==> default: network to not work properly. If the network doesn't work
  14. ==> default: properly, try changing this IP.
  15. ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
  16. ==> default: A newer version of the box 'bento/ubuntu-16.04' is available! You currently
  17. ==> default: have version '2.3.0'. The latest is version '2.3.1'. Run
  18. ==> default: `vagrant box update` to update.
  19. ==> default: Setting the name of the VM: kitchen-hwk-default-ubuntu-1604_default_1480787084932_41047
  20. Vagrant cannot forward the specified ports on this VM, since they
  21. would collide with some other application that is already listening
  22. on these ports. The forwarded port to 8123 is already in use
  23. on the host machine.
  24.  
  25. To fix this, modify your current project's Vagrantfile to use another
  26. port. Example, where '1234' would be replaced by a unique host port:
  27.  
  28. config.vm.network :forwarded_port, guest: 80, host: 1234
  29.  
  30. Sometimes, Vagrant will attempt to auto-correct this for you. In this
  31. case, Vagrant was unable to. This is usually because the guest machine
  32. is in a state which doesn't allow modifying port forwarding. You could
  33. try 'vagrant reload' (equivalent of running a halt followed by an up)
  34. so vagrant can attempt to auto-correct this upon booting. Be warned
  35. that any unsaved work might be lost.
  36. >>>>>> ------Exception-------
  37. >>>>>> Class: Kitchen::ActionFailed
  38. >>>>>> Message: 1 actions failed.
  39. >>>>>> Failed to complete #create action: [Expected process to exit with [0], but received '1'
  40. ---- Begin output of vagrant up --no-provision --provider virtualbox ----
  41. STDOUT: Bringing machine 'default' up with 'virtualbox' provider...
  42. ==> default: You assigned a static IP ending in ".1" to this machine.
  43. ==> default: This is very often used by the router and can cause the
  44. ==> default: network to not work properly. If the network doesn't work
  45. ==> default: properly, try changing this IP.
  46. ==> default: Importing base box 'bento/ubuntu-16.04'...
  47. ==> default: Matching MAC address for NAT networking...
  48. ==> default: You assigned a static IP ending in ".1" to this machine.
  49. ==> default: This is very often used by the router and can cause the
  50. ==> default: network to not work properly. If the network doesn't work
  51. ==> default: properly, try changing this IP.
  52. ==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
  53. ==> default: A newer version of the box 'bento/ubuntu-16.04' is available! You currently
  54. ==> default: have version '2.3.0'. The latest is version '2.3.1'. Run
  55. ==> default: `vagrant box update` to update.
  56. ==> default: Setting the name of the VM: kitchen-hwk-default-ubuntu-1604_default_1480787084932_41047
  57. STDERR: Vagrant cannot forward the specified ports on this VM, since they
  58. would collide with some other application that is already listening
  59. on these ports. The forwarded port to 8123 is already in use
  60. on the host machine.
  61.  
  62. To fix this, modify your current project's Vagrantfile to use another
  63. port. Example, where '1234' would be replaced by a unique host port:
  64.  
  65. config.vm.network :forwarded_port, guest: 80, host: 1234
  66.  
  67. Sometimes, Vagrant will attempt to auto-correct this for you. In this
  68. case, Vagrant was unable to. This is usually because the guest machine
  69. is in a state which doesn't allow modifying port forwarding. You could
  70. try 'vagrant reload' (equivalent of running a halt followed by an up)
  71. so vagrant can attempt to auto-correct this upon booting. Be warned
  72. that any unsaved work might be lost.
  73. ---- End output of vagrant up --no-provision --provider virtualbox ----
  74. Ran vagrant up --no-provision --provider virtualbox returned 1] on default-ubuntu-1604
  75. >>>>>> ----------------------
  76. >>>>>> Please see .kitchen/logs/kitchen.log for more details
  77. >>>>>> Also try running `kitchen diagnose --all` for configuration
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement