Using Vagrant Container Development Kit Plugins'Ĥ.1. Using Vagrant Container Development Kit Plugins'Ĭollapse section '4. Using Vagrant Container Development Kit PluginsĮxpand section '4. Installing Red Hat Container Development Kitģ. Understanding Container Development Kit Documentationġ.4.1. Introducing Red Hat Container Development Kit'ġ.1. Introducing Red Hat Container Development Kit'Ĭollapse section '1. Introducing Red Hat Container Development KitĮxpand section '1. nodes = [ end end end end end if provision_nodes = 'yes' config. # which is 1vCPU/512mb.So if setting custom requirements # only define any node which requires more than the defaults. # - Define number of nodes to spin up - N = 1 # - Define any custom memory/cpu requirement - # if custom requirements are desired.ensure to set # custom_cpu_mem = 'yes' otherwise set to 'no' # By default if custom requirements are defined and set below # any node not defined will be configured as the default. Please don't change it unless you know what # you're doing. The '2' in nfigure # configures the configuration version (we support older styles for # backwards compatibility). # -*- mode: ruby -*- # vi: set ft=ruby : # All Vagrant configuration is done below. Start leveraging you can do so by doing the following… You can check these out on GitHubĪnd if you are interested in pulling these templates down from GitHub to I have also been saving these as templates on GitHub which also includesĪ consistent and customizable Vagrantfile for each distro ready forĬonsumption.

You can check out the actual Vagrant boxes on Hashicorp’s Atlas site In this post I want to share those templates with others as wellĪs share some little tricks I have learned for myself that have proven To have a standard methodology for building them as well as consuming Templates based on different Linux distros all using Packer. Over the past few months I have been putting together some Vagrant box

Vagrant box list