Install vagrant vmware workstation provider


Solution for Vagrant VMware Provider install


 D:\ubuntu>Vagrant up --provider=vmware_workstation

The provider 'vmware_workstation' could not be found, but was requested to

back the machine 'default'. Please use a provider that exists.


Vagrant knows about the following providers: docker, hyperv, virtualbox


D:\ubuntu>vagrant plugin install vagrant-vmware-desktop

Installing the 'vagrant-vmware-desktop' plugin. This can take a few minutes...

ERROR:  SSL verification error at depth 3: unable to get local issuer certificate (20)

ERROR:  You must add /C=US/O=Starfield Technologies, Inc./OU=Starfield Class 2 Certification Authority to your local trusted store

Vagrant failed to load a configured plugin source. This can be caused

by a variety of issues including: transient connectivity issues, proxy

filtering rejecting access to a configured plugin source, or a configured

plugin source not responding correctly. Please review the error message

below to help resolve the issue:


  SSL_connect SYSCALL returned=5 errno=0 peeraddr=18.165.32.97:443 state=error: certificate verify failed (https://gems.hashicorp.com/specs.4.8.gz)


Source: https://gems.hashicorp.com/


D:\ubuntu>vagrant plugin install --plugin-clean-sources --plugin-source https://rubygems.org vagrant-vbguest

Installing the 'vagrant-vbguest' plugin. This can take a few minutes...

Fetching micromachine-3.0.0.gem

Fetching vagrant-vbguest-0.31.0.gem

Installed the plugin 'vagrant-vbguest (0.31.0)'!


D:\ubuntu>vagrant plugin install --plugin-clean-sources vagrant-vmware-desktop

Installing the 'vagrant-vmware-desktop' plugin. This can take a few minutes...

Fetching vagrant-vmware-desktop-3.0.3.gem

Installed the plugin 'vagrant-vmware-desktop (3.0.3)'!


D:\ubuntu>Vagrant up --provider=vmware_workstation

Bringing machine 'default' up with 'vmware_workstation' provider...

==> default: Box 'hashicorp/bionic64' could not be found. Attempting to find and install...

    default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation

    default: Box Version: >= 0

==> default: Loading metadata for box 'hashicorp/bionic64'

    default: URL: https://vagrantcloud.com/hashicorp/bionic64

==> default: Adding box 'hashicorp/bionic64' (v1.0.282) for provider: vmware_desktop

    default: Downloading: https://vagrantcloud.com/hashicorp/boxes/bionic64/versions/1.0.282/providers/vmware_desktop.box

    default:

==> default: Successfully added box 'hashicorp/bionic64' (v1.0.282) for 'vmware_desktop'!

==> default: Cloning VMware VM: 'hashicorp/bionic64'. This can take some time...

==> default: Checking if box 'hashicorp/bionic64' version '1.0.282' is up to date...

==> default: Verifying vmnet devices are healthy...

==> default: Preparing network adapters...

==> default: Starting the VMware VM...

==> default: Waiting for the VM to receive an address...

==> default: Forwarding ports...

    default: -- 22 => 2222

==> 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: Configuring network adapters within the VM...

==> default: Waiting for HGFS to become available...

==> default: Enabling and configuring shared folders...

    default: -- D:/ubuntu: /vagrant


D:\ubuntu>Vagrant ssh

Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-58-generic x86_64)


 * Documentation:  https://help.ubuntu.com

 * Management:     https://landscape.canonical.com

 * Support:        https://ubuntu.com/advantage


  System information as of Sat Jun  3 01:54:07 UTC 2023


  System load:  0.5               Processes:           97

  Usage of /:   2.6% of 61.80GB   Users logged in:     0

  Memory usage: 15%               IP address for eth0: 192.168.56.153

  Swap usage:   0%



0 packages can be updated.

0 updates are security updates.


Comments

Post a Comment

Popular posts from this blog

Hyper-V Network NAT Configuration

Image
  How to Create a NAT Switch on Hyper-V Published on: July 12, 2022   by  Robert Allen In this guide, you will learn how to create a Hyper-V switch that uses NAT for network access. NAT will provide virtual machines access to network resources (internet access) using the host computers network adapter. For this guide, I’ll use the below network settings. When the configuration is complete the VMs on the  192.168.100.0/24  network will use the Hyper-V Host IP  192.168.1.4  for accessing the internet. Step 1: Create an Internal Virtual Switch Open PowerShell and run the below command. Change “SWITCHNAME” to whatever you want to name your switch, I’ve called mine “nat-switch”. New-VMSwitch -Name SWITCHNAME -SwitchType Internal Step 2: Get the Interface Index Number (ifIndex) Next, you need to find the index number of the virtual switch created in step 1. Run the below command. Get-NetAdapter My index number is 28, you will probably have a different number...
Read more

Larvel blade script to print number tables

      <table style='table-layout: fixed; width:100%;' border=1>         <tr>             @for ($i = 1; $i <= 20; $i++)                 <td>                     @for ($j = 1; $j <= 10; $j++)                         {{ $i }} {{ '*' }} {{ $j }}                         {{ '=' }}{{ $i * $j }};                         <br>                     @endfor                 </td>                 @if ($i % 10 == 0)         </tr>         @endif       ...
Read more