[GitHub] [incubator-openwhisk] Bobyuan1015 opened a new issue #4383: Vagrant way cannot run, connection between host with virtualbox can not be able to be built.

[GitBox <gi...@apache.org>]

Bobyuan1015 opened a new issue #4383: Vagrant way cannot run, connection between host with virtualbox can not be able to be built.
URL: https://github.com/apache/incubator-openwhisk/issues/4383
 
 
   bob@bob:~/vagrant$ ./hello
   Installing the 'vagrant-disksize' plugin. This can take a few minutes...
   Installed the plugin 'vagrant-disksize (0.1.3)'!
   Bringing machine 'default' up with 'virtualbox' provider...
   ==> default: Box 'ubuntu/xenial64' could not be found. Attempting to find and install...
       default: Box Provider: virtualbox
       default: Box Version: >= 0
   ==> default: Loading metadata for box 'ubuntu/xenial64'
       default: URL: https://vagrantcloud.com/ubuntu/xenial64
   ==> default: Adding box 'ubuntu/xenial64' (v20190320.0.0) for provider: virtualbox
       default: Downloading: https://vagrantcloud.com/ubuntu/boxes/xenial64/versions/20190320.0.0/providers/virtualbox.box
       default: Download redirected to host: cloud-images.ubuntu.com
   ==> default: Successfully added box 'ubuntu/xenial64' (v20190320.0.0) for 'virtualbox'!
   ==> default: Importing base box 'ubuntu/xenial64'...
   ==> default: Matching MAC address for NAT networking...
   ==> default: Checking if box 'ubuntu/xenial64' version '20190320.0.0' is up to date...
   ==> default: Setting the name of the VM: whisk-1903221037
   Vagrant is currently configured to create VirtualBox synced folders with
   the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
   guest is not trusted, you may want to disable this option. For more
   information on this option, please refer to the VirtualBox manual:
   
     https://www.virtualbox.org/manual/ch04.html#sharedfolders
   
   This option can be disabled globally with an environment variable:
   
     VAGRANT_DISABLE_VBOXSYMLINKCREATE=1
   
   or on a per folder basis within the Vagrantfile:
   
     config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
   ==> default: Clearing any previously set network interfaces...
   ==> default: Preparing network interfaces based on configuration...
       default: Adapter 1: nat
       default: Adapter 2: hostonly
   ==> default: Forwarding ports...
       default: 22 (guest) => 2222 (host) (adapter 1)
   ==> default: Running 'pre-boot' VM customizations...
   ==> default: Resized disk: old 10240 MB, req 51200 MB, new 51200 MB
   ==> default: You may need to resize the filesystem from within the guest.
   ==> default: Booting VM...
   ==> default: Waiting for machine to boot. This may take a few minutes...
       default: SSH address: 127.0.0.1:2222
       default: SSH username: vagrant
       default: SSH auth method: private key
   Timed out while waiting for the machine to boot. This means that
   Vagrant was unable to communicate with the guest machine within
   the configured ("config.vm.boot_timeout" value) time period.
   
   If you look above, you should be able to see the error(s) that
   Vagrant had when attempting to connect to the machine. These errors
   are usually good hints as to what may be wrong.
   
   If you're using a custom box, make sure that networking is properly
   working and you're able to connect to the machine. It is a common
   problem that networking isn't setup properly in these boxes.
   Verify that authentication configurations are also setup properly,
   as well.
   
   If the box appears to be booting properly, you may want to increase
   the timeout ("config.vm.boot_timeout") value.
   bob@bob:~/vagrant$ 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services