sloopstash / kickstart-linux Goto Github PK

Hi Team,

I got the below error message while trying to up the ubuntu-linux-22-04.
VAGRANT_CWD=./vagrant/ubuntu-linux-22-04/virtualbox/amd64/server Vagrant up

sloopstash-ubuntu-linux-22-04-server: SSH auth method: private key
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
sloopstash-ubuntu-linux-22-04-server: Warning: Authentication failure. Retrying...
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.

Also I checked there is config.vm.boot_timeout value configured.

And VAGRANT_CWD=./vagrant/ubuntu-linux-22-04/virtualbox/amd64/server Vagrant ssh is working and login into VM.

Is there any reason for this Warning: Authentication failure. Retrying... error message.

export OS_NAME=alma-linux-9
export OS_ARCHITECTURE=amd64
export OS_EDITION=server
export HYPERVISOR=virtualbox

Then I started the command VAGRANT_CWD=./vagrant/$OS_NAME/$HYPERVISOR/$OS_ARCHITECTURE/$OS_EDITION vagrant up from the kickstart-linux directory.

The installation or boot is interrupted by the warning : SSH authentication failure warning for Alma Linux 9.

Bringing machine 'sloopstash-ubuntu-linux-18-04-server' up with 'vmware_fusion' provider...
==> sloopstash-ubuntu-linux-18-04-server: Box 'sloopstash/ubuntu-linux-18-04' could not be found. Attempting to find and install...
    sloopstash-ubuntu-linux-18-04-server: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
    sloopstash-ubuntu-linux-18-04-server: Box Version: 1.1.1
==> sloopstash-ubuntu-linux-18-04-server: Loading metadata for box 'sloopstash/ubuntu-linux-18-04'
    sloopstash-ubuntu-linux-18-04-server: URL: https://vagrantcloud.com/api/v2/vagrant/sloopstash/ubuntu-linux-18-04
The box you're attempting to add doesn't support the provider
you requested. Please find an alternate box or use an alternate
provider. Double-check your requested provider to verify you didn't
simply misspell it.

If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is
released.

Name: sloopstash/ubuntu-linux-18-04
Address: https://vagrantcloud.com/api/v2/vagrant/sloopstash/ubuntu-linux-18-04
Requested provider: vmware_desktop vmware_fusion vmware_workstation (arm64)

I got this error when running vagrant up in the folder kickstart-linux/vagrant/ubuntu-linux-18-04/vmware/amd64/server

Add support to build, run, and manage a Rocky Linux 8 server VM using Vagrant and VirtualBox hypervisor.

• Windows
• Ubuntu Linux

Add support to build, run, and manage a Alma Linux 8 server VM using Vagrant and VMware Fusion hypervisor.

• Mac (Intel processor)
• Mac (Apple M1/M2 processor)

I followed the steps mentioned in Kickstart-Linux wiki home page and installed the Vagrant and Virtualbox as mentioned in the document. I'm trying to boot the ubuntu-linux-18-04 server. I'm facing an error.

Vagrant version : 2.2.9
Virtualbox version : 6.1.36
OS : Windows 11
Processor : i5
Memory : 8GB

Divya@DESKTOP-5QK0EFI MINGW64 /opt/kickstart-linux (master)
$ VAGRANT_CWD=./vagrant/ubuntu-linux-18-04/virtualbox/amd64/server vagrant up
Bringing machine 'sloopstash-ubuntu-linux-18-04-server' up with 'virtualbox' provider...
==> sloopstash-ubuntu-linux-18-04-server: Clearing any previously set forwarded ports...
==> sloopstash-ubuntu-linux-18-04-server: Fixed port collision for 22 => 2222. Now on port 2200.
==> sloopstash-ubuntu-linux-18-04-server: Clearing any previously set network interfaces...
==> sloopstash-ubuntu-linux-18-04-server: Preparing network interfaces based on configuration...
    sloopstash-ubuntu-linux-18-04-server: Adapter 1: nat
    sloopstash-ubuntu-linux-18-04-server: Adapter 2: hostonly
==> sloopstash-ubuntu-linux-18-04-server: Forwarding ports...
    sloopstash-ubuntu-linux-18-04-server: 22 (guest) => 2200 (host) (adapter 1)
==> sloopstash-ubuntu-linux-18-04-server: Running 'pre-boot' VM customizations...
==> sloopstash-ubuntu-linux-18-04-server: Booting VM...
==> sloopstash-ubuntu-linux-18-04-server: Waiting for machine to boot. This may take a few minutes...
    sloopstash-ubuntu-linux-18-04-server: SSH address: 127.0.0.1:2200
    sloopstash-ubuntu-linux-18-04-server: SSH username: vagrant
    sloopstash-ubuntu-linux-18-04-server: 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.

Add support to build, run, and manage a Rocky Linux 8 server VM using Vagrant and VMware Fusion hypervisor.

• Mac (Intel processor)
• Mac (Apple M1/M2 processor)

Add support to build, run, and manage a Rocky Linux 9 server VM using Vagrant and VMware Fusion hypervisor.

• Mac (Intel processor)
• Mac (Apple M1/M2 processor)

Add support to build, run, and manage a Rocky Linux 9 server VM using Vagrant and VirtualBox hypervisor.

• Windows
• Ubuntu Linux

Add support to build, run, and manage a Amazon Linux 2 server VM using Vagrant and VMware Fusion hypervisor.

• Mac (Intel processor)
• Mac (Apple M1/M2 processor)

Hi, I followed the instructions in your article ( https://sloopstash.com/blog/how-to-build-vm-on-apple-m1-m2-chip-mac-with-vmware-fusion-and-vagrant.html ), however I still end up with this error:

Bringing machine 'sloopstash-ubuntu-linux-22-04-server' up with 'vmware_fusion' provider...
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.

When attempting to launch an Ubuntu 18.04 virtual machine (VM) using Vagrant, an error occurs indicating a failure in executing VBoxManage, which is a command-line interface (CLI) tool utilized by Vagrant for managing VirtualBox.

Error

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "ec604649-1667-4464-a5d3-d6e51d2f90ec", "--type", "headless"]

Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3' (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Add support to build, run, and manage a Amazon Linux 2 server VM using Vagrant and VirtualBox hypervisor.

• Windows
• Ubuntu Linux

I was trying to install docker and I was trying to do it from the prerequisites from the Linux and I’m stuck at this point

/opt/kickstart-linux (master)
$ VAGRANT_CWD=./vagrant/ubuntu-linux-18-04/virtualbox/amd64/server vagrant up
Bringing machine 'sloopstash-ubuntu-linux-18-04-server' up with 'virtualbox' provider...
==> sloopstash-ubuntu-linux-18-04-server: Box 'sloopstash/ubuntu-linux-18-04' could not be found. Attempting to find and install...
sloopstash-ubuntu-linux-18-04-server: Box Provider: virtualbox
sloopstash-ubuntu-linux-18-04-server: Box Version: 1.1.1
The box 'sloopstash/ubuntu-linux-18-04' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
vagrant login. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://vagrantcloud.com/sloopstash/ubuntu-linux-18-04"]
Error: SSL certificate problem: unable to get local issuer certificate

Add support to build, run, and manage a Alma Linux 9 server VM using Vagrant and VirtualBox hypervisor.

• Windows
• Ubuntu Linux

Add support to build, run, and manage a Ubuntu Linux 22.04 server VM using Vagrant and VMware Fusion hypervisor.

• Mac (Intel processor)
• Mac (Apple M1/M2 processor)

Add support to build, run, and manage a Alma Linux 8 server VM using Vagrant and VirtualBox hypervisor.

• Windows
• Ubuntu Linux

Add support to build, run, and manage a Alma Linux 9 server VM using Vagrant and VMware Fusion hypervisor.

• Mac (Intel processor)
• Mac (Apple M1/M2 processor)

Need to reorganize the directory structure based on operating systems, Vagrant providers, and architecture.