Open athajaerel opened 4 days ago
Box notes:
? The first network interface (adapter 1) must be a NAT adapter. Vagrant uses this to connect the first time. (could be VMware specific)
? The MAC address of the first network interface (the NAT adapter) should be noted, since you will need to put it in a Vagrantfile later as the value for config.vm.base_mac. (could be VMware specific)
? $ vagrant package --base my-virtual-machine (hmm, built-in packager? vbox specific?)
Where "my-virtual-machine" is replaced by the name of the virtual machine in VirtualBox to package as a base box.
A base box typically consists of only a bare minimum set of software for Vagrant to function. As an example, a Linux box may contain only the following:
Package manager
SSH
SSH user so Vagrant can connect
Perhaps Chef, Puppet, etc. but not strictly required.
By default, Vagrant expects a "vagrant" user to SSH into the machine as. This user should be setup with the insecure keypairs that Vagrant uses as a default to attempt to SSH. It should belong to a group named "vagrant". Also, even though Vagrant uses key-based authentication by default, it is a general convention to set the password for the "vagrant" user to "vagrant". This lets people login as that user manually if they need to.
Root Password: "vagrant"
Password-less Sudo
In order to keep SSH speedy even when your machine or the Vagrant machine is not connected to the internet, set the UseDNS configuration to no in the SSH server configuration.
Let's try to create the tiniest possible still-viable Void VM.
Alternatively, give Terraform another chance.
What about Vagrant? Does that work with libvirt?