CoderVagrant's profile picture. Just a coder learning Vagrant.
Not associated to HashiCorp. Opinions are my own, reflecting my views at that point in time and can change.
Let the coding begin!

coder-learning-vagrant

@CoderVagrant

Just a coder learning Vagrant. Not associated to HashiCorp. Opinions are my own, reflecting my views at that point in time and can change. Let the coding begin!

Yeah... nah... couldn't stop myself. So... turns out that I had to set it up in .bashrc (don't have .bash_profile in elementary OS) using export VAGRANT_HOME=<path> Also changed the VirtualBox VMs folder (VirtualBox --> Preferences)


Uh... this thing about moving the Vagrant home folder outside Linux's home folder... ain't working so well for me. Gotta take a look at it tomorrow.


And... finally, with the box downloaded... vagrant init theshellland/elementaryos-5.0-juno and vagrant up


OK, minor setback... the vagrant version available OOTB for elementary OS (and perhaps Ubuntu) is a bit old... (2.0.x). Plan B: remove OOTB vagrant, download .deb package and install it (new version 2.2.5)


Generating the Vagrantfile vagrant init theshellland/elementaryos-5.0-juno


Let's try downloading an elementary OS box: vagrant box add theshellland/elementaryos-5.0-juno


Wanna delete a box? vagrant box remove <box> [--provider <provider>]


Repackaging a box sounds interesting... will look it up at a later stage


Wanna know what boxes are available? vagrant box list


The --force flag removes any already existing box with the same name


How to download a box? Not too hard... vagrant box add <base box> --force This command downloads a base box


vagrant init <base box name> <fallback URL>


The URL pointing to the box is called fallback URL


Vagrantfile seems to have references to the Vagrant version, the box to be used and the URL to download that box (if required)


VMs are setup based on a 'base box', specially packaged version of the OS "with some specific configurations in place"


VirtualBox installed ✔️


Vagrant configuration, Puppet and Chef manifests are written in Ruby DSL... great... straight into GitHub (once I start writing them)


First question: are providers simply... hypervisors?


Vagrant uses providers (?) to integrate with the third-party virtualisation software, which provides the VMs for our dev environment


United States Trends

Loading...

Something went wrong.


Something went wrong.