The capability 'nfs_mount' could not be found. This is an internal error
that users should never see. Please report a bug.
Cmd
C:\var\www\cc-dev-env>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Clearing any previously set forwarded ports...
==> 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: 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
default: Warning: Remote connection disconnect. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 4.3.36
default: VirtualBox Version: 5.0
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] found entry for: 192.168.100.100 cc.dev
==> default: Mounting NFS shared folders from guest...
The capability 'nfs_mount' could not be found. This is an internal error
that users should never see. Please report a bug.
I am using
Windows 10 64-bit
Vagrant 1.8.1
vagrant-hostsupdater (1.0.2)
vagrant-nfs_guest (0.1.8)
vagrant-share (1.1.5, system)
vagrant-winnfsd (1.1.0)
Of course I would like to not see this error and see the VM that I am trying to boot open.
Related
I am trying to run an example machine learning pipeline on premise (meaning: locally on a Windows 10 laptop) using MiniKF and Kubeflow Pipelines, following this tutorial, but I can't reach the site that should appear at http://10.10.10.10.
I installed:
Virtualbox 6.1.4
Vagrant 2.2.7
Then, in a CMD prompt, I ran:
C:\Users\jervan\Documents\minikf>vagrant init arrikto/minikf
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
C:\Users\jervan\Documents\minikf>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Using C:/Users/jervan/Documents/minikf/minikf-user-data.vdi for persistent storage.
==> default: Importing base box 'arrikto/minikf'...
==> default: Generating MAC address for NAT networking...
==> default: Using C:/Users/jervan/Documents/minikf/minikf-user-data.vdi for persistent storage.
==> default: Checking if box 'arrikto/minikf' version '20200305.1.0' is up to date...
==> default: Setting the name of the VM: minikf_default_1584993248035_85721
==> 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: 32123 (guest) => 32123 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Using C:/Users/jervan/Documents/minikf/minikf-user-data.vdi for persistent storage.
==> default: Running 'pre-boot' VM customizations...
==> default: Using C:/Users/jervan/Documents/minikf/minikf-user-data.vdi for persistent storage.
==> default: ** Creating persistent storage **
==> default: Using C:/Users/jervan/Documents/minikf/minikf-user-data.vdi for persistent storage.
==> default: ** Attaching persistent storage **
==> 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
default: Warning: Connection reset. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 6.0.14_Ubuntu r132055
default: VirtualBox Version: 6.1
==> default: Using C:/Users/jervan/Documents/minikf/minikf-user-data.vdi for persistent storage.
==> default: ** Managing persistent storage **
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
default: /vagrant => C:/Users/jervan/Documents/minikf
==> default: Machine 'default' has a post `vagrant up` message. This is a message
==> default: from the creator of the Vagrantfile, and not from Vagrant itself:
==> default:
==> default: Welcome to MiniKF!
==> default: Visit http://10.10.10.10/ to get started.
==> default:
But when I visit http://10.10.10.10 I get an "This site can’t be reached. 10.10.10.10 took too long to respond." error.
My Virtualbox settings look like this:
I can ssh into the box like so:
C:\Users\jervan\Documents\minikf>vagrant ssh
Last login: Mon Mar 23 13:14:17 2020 from 10.0.2.2
Welcome to MiniKF!
Type "minikf" to ensure everything is up and running.
vagrant#minikf:~$
and when I type minikf I get the MiniKF Provisioing tool (which is what you would normally see embedded in the MiniKF landing page).
After provisioning the software, I see pods starting up and the message "Kubeflow is deployed". But after the "exposing services" stage, I see errors popping up:
If I click on enter then the errors disappear, and the "Provisioning completed." screen with username and password appears.
If I go to VirtualBox and click on the green arrow, then it shows me the ubuntu login page, but I don't manage to login with the credentials shown in the previous step.
I had a similar issue.
First time around, it fails to start and after I run vagrant up again it starts, but I cannot access 10.10.10.10
errors I had
Then I went into the vm itself and shut it down like this :
shutting down the VM
After shutting it down manually, I did vagrant up again and now I can access 10.10.10.10
I'm attempting to set a virtual machine enviroment using vagrant.
I've done a couple of tries with different boxes via vagrantcloud.com, BUT I'm always getting stuck when I try to launch this box: I added a URL on vagrant file for downloads https://app.vagrantup.com/ubuntu/boxes/trusty64, but i doesnt seem to work
λ vagrant init x9 ubuntu/boxes/bionic64
λ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
default: Box 'x9' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
default: Box file was not detected as metadata. Adding it directly... default: Adding box 'x9' (v0) for provider: virtualbox
default: Downloading: https://app.vagrantup.com/ubuntu/boxes/bionic64
default:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Failed to connect to app.vagrantup.com port 443: Timed out
Anyone knows how do I proceed ?
it's normal it cannot find this box if you haven't downloaded it yet.
I tried and it works perfect, it downloads and start the box, i share you my basic config (which is what i tested)
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/bionic64"
end
This is my output:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'ubuntu/bionic64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'ubuntu/bionic64'
default: URL: https://vagrantcloud.com/ubuntu/bionic64
==> default: Adding box 'ubuntu/bionic64' (v20200304.0.0) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/ubuntu/boxes/bionic64/versions/20200304.0.0/providers/virtualbox.box
==> default: Box download is resuming from prior download progress
default: Download redirected to host: cloud-images.ubuntu.com
==> default: Successfully added box 'ubuntu/bionic64' (v20200304.0.0) for 'virtualbox'!
==> default: Importing base box 'ubuntu/bionic64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/bionic64' version '20200304.0.0' is up to date...
==> default: Setting the name of the VM: amos_default_1583767787636_71616
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
default: The guest additions on this VM do not match the installed version of
default: VirtualBox! In most cases this is fine, but in rare cases it can
default: prevent things such as shared folders from working properly. If you see
default: shared folder errors, please make sure the guest additions within the
default: virtual machine match the version of VirtualBox you have installed on
default: your host and reload your VM.
default:
default: Guest Additions Version: 5.2.34
default: VirtualBox Version: 6.1
==> default: Mounting shared folders...
default: /vagrant => /home/amos
The only possible explanation is that you have bad internet connection...try to do a speed test here:
https://www.speedtest.net/
if you have bad connection try restart your modem or contact your internet provider
My problem
I'm fairly new to Vagrant, so apologies if this question is rudimentary.
I am trying to inspect Nomad, which in turn requires Vagrant to run. I have spawned a new Ubuntu 16 machine on EC2, installed virtualbox and Vagrant, and entered vagrant up as instructed:
$ vagrant up
VirtualBox is complaining that the installation is incomplete. Please
run `VBoxManage --version` to see the error message which should contain
instructions on how to fix this error.
ubuntu#ip-172-31-26-135:~/vagrant_config$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-16.04' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'bento/ubuntu-16.04'
default: URL: https://vagrantcloud.com/bento/ubuntu-16.04
==> default: Adding box 'bento/ubuntu-16.04' (v2.3.8) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/bento/boxes/ubuntu-16.04/versions/2.3.8/providers/virtualbox.box
==> default: Successfully added box 'bento/ubuntu-16.04' (v2.3.8) for 'virtualbox'!
==> default: Importing base box 'bento/ubuntu-16.04'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'bento/ubuntu-16.04' is up to date...
==> default: Setting the name of the VM: vagrant_config_default_1502307080428_76965
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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.
What have I tried
Rebooting the AWS VM
Checking for disk full / High memory / High CPU usage (found nothing)
Removing the vagrant box and re-installing it
Re-provisioning
My question
How to handle ssh timeout with Vagrant on an Ubuntu 16 EC2 Machine?
Sort of unrelated, but Nomad does not require Vagrant. You can run nomad on any machine, just download the binary(https://www.nomadproject.io/downloads.html) and run it.
I wanted to stand up a local instance of Openshift, but vagrant up doesn't finish.
I downloaded cdk-2.2.0.zip and rhel-cdk-kubernetes-7.2-29.x86_64.vagrant-virtualbox.box from developers.redhat.com.
Running vagrant up after installation gets stuck at Configuring and enabling network interfaces...:
me:~/cdk/components/rhel/rhel-ose $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'cdkv2'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: rhel-ose_default_1476736433516_4922
==> 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: 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
default: Warning: Remote connection disconnect. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Registering box with vagrant-registration...
default: Would you like to register the system now (default: yes)? [y|n]y
default: username: me#email.com
default: password:
==> default: Registration successful.
==> default: Checking for guest additions in VM...
default: No guest additions were detected on the base box for this VM! Guest
default: additions are required for forwarded ports, shared folders, host only
default: networking, and more. If SSH fails on this machine, please install
default: the guest additions and repackage the box to continue.
default:
default: This is not an error message; everything may continue to work properly,
default: in which case you may ignore this message.
==> default: Configuring and enabling network interfaces...
Any ideas how to troubleshoot this? Not sure if it's vagrant or the VM or something else.
Thank you for your time!
Same happened to me but after updating Vagrant to 1.9.1 version the problem was solved.
I am using OSX but it might be the same for all others OS.
the easiest is to install the vagrant vbguest plugin and let it install and configure the Virtual Box Guest Addition for the right version of your VirtualBox
I am trying to run Laravel Homestead box on DigitalOcean's Ubuntu 14.04 LEMP droplet. I'm following these two tutorials:
How to install Vagrant on a VPS Running Ubuntu 12.04
Laravel Homestead
But I can't seem to start up the box after the installation. I keep getting this error message:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Setting the name of the VM: homestead
==> 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: 80 => 22280 (adapter 1)
default: 443 => 22443 (adapter 1)
default: 3306 => 23306 (adapter 1)
default: 5432 => 25432 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
Here is my VirtualBox's error log:
VirtualBox log