martinandersson / box-ubuntu-budgie-19.10

A Vagrant box with Ubuntu Budgie 19.10.

A Vagrant box with Ubuntu Budgie 19.10

The artifacts of this project are two .box files with Ubuntu Budgie 19.10 installed; one file for the VirtualBox provider, and one for VMware.

You don't have to run weird-ass Linux commands to get the artifacts. They are already built and uploaded [manually] to Vagrant's cloud as pristine/ubuntu-budgie-19.10¹.

This GitHub project is used as 1) an issue tracker, 2) changelog and 3) as an authoritative source on how exactly the box was built.

_{¹ These Vagrant boxes are often labeled as "minimal" and/or "base". I refrain from using either term since a box that is 1.9 GB in size is hardly "minimal" nor am I convinced that all use-cases of this box are to derive yet another box as implied by the word "base". We are building a box. Period.}

Using the box

Make sure you have Vagrant and at least one of the supported VM providers installed², then in theory, all you should have to do in order to get a Virtual Machine up and running with Ubuntu Budgie 19 is:

vagrant init pristine/ubuntu-budgie-19.10
vagrant up

_{² Can not really recommend anyone. Both VirtualBox and VMware suck equally much. Okay, VMware sucks a little bit less.}

Building the box

To build the boxes using Packer, do this:

packer build template.json

Or, one provider at a time:

packer build -only virtualbox-iso template.json

..best of luck to you. template.json's "boot command" uses VNC to literally click on the installer's GUI buttons in order to install the OS. This procedure is extremely host-machine dependent with wait-settings tailored to my particular host machine. I.e., I would be surprised if you can run the previously quoted commands without any issues. In particular, you should prolly only build an image for one provider at a time.