Check out my upgraded Vagrant project

Martien van den Akker
2 min readFeb 25, 2022

Update: january 15th, 2024: Last week cleaned up my Vagrant repository. In stead of the mentioned CentOS Fuse projects, check out my current Oracle Linux 8 Develop project.

My first article on Medium was about Getting started with Red Hat Fuse Development Environment. This article describes how I created a Vagrant project to do my Fuse development in. For years now, I use Virtual Machines to abstract my installations from my host, keeping my host OS clean. A few years ago, I adopted the Vagrant way of provisioning. Since then I wrote several articles on my learning path of Vagrant.

I sort of forked my Vagrant project to support my Red Hat Fuse Development environment for my colleagues. But, it is not handy to have two of those projects. Lately, I upgraded my CentOS 7.8 Red Hat Fuse Vagrant project to a CentOS 8 Stream Red Hat Fuse environment. And now it’s time to share it with the world.

This makes it easier for me to write about my findings and new versions of scripts and applications I use. Also, it saves room on my laptop, not having to keep several copies of install binaries.

Check out my CentOS 8 Stream Red Hat Fuse vagrant project, it works smooth (on my hexacore 32GB laptop that is). It should run on a 16GB laptop with 4 cores. Adapt the settings.yml to 12GB of memory and 4 cores, before startup. Also, check the provisioners.yml for the applications you want to install. Each provisioner has a run element. These can have the following values:

  • once: the provisioner is executed once at first startup
  • never: the provisioner will not automatically be executed
  • always: the provisioner will be executed at every startup

Every provisioner in the provisioners.yml can be executed explicitly by executing:

Where provisioner-name is the value of the name element of the provisioner provisioners.yml.

Read the README.md for more information.

--

--

Martien van den Akker

Technology Architect at Oracle Netherlands. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle