Workaround for PUP-6134

Tom Kishel



10,038 latest version

5.0 quality score

Version information

  • 1.1.1 (latest)
  • 1.0.7
  • 1.0.6
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
released Sep 26th 2018
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet > 4.7.0 < 7.0.0
  • Windows

Start using this module


tkishel/system_gem — version 1.1.1 Sep 26th 2018


Table of Contents

  1. Description
  2. Usage - Configuration options and additional functionality
  3. Reference - An under-the-hood peek at what the module is doing and how
  4. Limitations


This a workaround for PUP-6134:

Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows


Install this module, and specify system_gem as the provider of gem packages.

package { 'sinatra':
  ensure   => present,
  provider => system_gem,

Once PUP-6134 has been resolved, specify gem as the provider of gem packages, and uninstall this module.


On Windows ...

Puppet is unable to manage a ruby gem anywhere other than in Puppet's ruby using the gem package provider. This is caused by Puppet prepending its paths (including the path to Puppet's ruby gem command) to PATH. This workaround removes Puppet's paths from PATH when setting :gemcmd.


While the system_gem package provider is meant as a workaround for an issue specific to Windows, it is compatible with the other operating systems supported by the parent gem package provider.