Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-3084

docker: puppetserver.conf PUPPETSERVER_MAX_ACTIVE_INSTANCES etc unhandled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Puppet Server
    • Labels:
      None
    • Template:
      PUP Bug Template
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Update:
      I misunderstood. The env-variables are set globally from docker run or docker-compose.
      No need to replace the "placeholders".
      Closing this ticket.


      Original report:
      This ticket should probably be fixed at the same time as SERVER-3083, since they are exactly the same, and the fix take place in the same file (45-update-puppetserver-conf.sh).

          # (optional) maximum number of JRuby instances to allow
          max-active-instances: ${PUPPETSERVER_MAX_ACTIVE_INSTANCES}
       
          # (optional) number of HTTP requests a given JRuby instance will handle in its lifetime
          max-requests-per-instance: ${PUPPETSERVER_MAX_REQUESTS_PER_INSTANCE}
      

      The two variables/placeholders above should be replaced with a custom or default value.

      Unlike $LOGDIR, the above two variables are described in the instructions at https://hub.docker.com/r/puppet/puppetserver but they don't seem to be used.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            elof Elof Ofel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support