3.8.2. Building SIMP From Tarball


Building SIMP from a pre-built tarball is the fastest method for getting a known stable build of a SIMP ISO and should be preferred over other methods. Getting Started


Please have your environment prepared as specified by Environment Preparation before continuing.

Download the SIMP release tarball, found on our SIMP artifacts repository.

Download the latest tarball according to your needs. If you are not sure what version you need, check the SIMP Version Guide. Generating The ISO

Clone simp-core:

$ git clone https://github.com/simp/simp-core

Change into the simp-core directory and make sure you are on the correct branch for your target SIMP version:

$ cd simp-core
$ git checkout tags/6.1.0-0 # for SIMP 6.1

Run bundle install to make sure that all of the build tools and dependencies are installed and up to date:

$ bundle install

Copy the pre-built tarball to the DVD_Overlay directory that corresponds with the version of base OS you want to build. For instance, if you wanted to build with CentOS-7,

$ cp </path/to/.tar> build/distributions/CentOS/7/x86_64/DVD_Overlay

Run the build:auto rake task to create a bootable ISO:


Do not add any whitespace before or after the commas. This is an artifact of using rake.

$ SIMP_ENV_NO_SELINUX_DEPS=yes bundle exec rake build:auto[<directory containing source ISOs>,6.X]

Build ENV vars:

  • SIMP_BUILD_docs - (yes|no) - Toggle doc builds.
    • The docs take a long time to build!
  • SIMP_ENV_NO_SELINUX_DEPS - (yes|no) - Force the earliest version of policycoreutils<-python> and selinux-policy<-devel> for the major EL release.
    • In order to maintain the backward compatibility of simp-rsync with each major EL release, we must bring in the selinux policies supplied by the original major EL release being built. SELinux policies are forward compatible during a major release, but not necessarily backwards compatible. If you opt to use repositories that bring in updated selinux policies, you will need to set this to YES.
  • BEAKER_destroy - (yes|no) - Setting BEAKER_destroy=no will preserve the docker container used to build SIMP.

Once the process completes, you should have a bootable SIMP ISO, in: build/distributions/<OS>/<rel>/<arch>/SIMP_ISO/