https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • y

    Yury Bushmelev

    06/16/2022, 2:00 AM
    I'd say follow steps from here: https://puppet.com/docs/puppet/7/install_agents.html#install_mac_agents
  • y

    Yury Bushmelev

    06/16/2022, 2:01 AM
    but answer for your question is here: https://puppet.com/docs/puppet/7/install_agents.html#configure_server_setting
  • c

    Christopher Afeku Junior

    06/16/2022, 7:37 AM
    Thank you for the assistance. I find one thing confusing tho. Complete these steps before attempting to install macOS agents. mv /opt/puppetlabs/puppet/bin/wrapper.sh /opt/puppetlabs/puppet/bin/wrapper This directory would only be available after the installation is complete if I'm not mistaken.
  • c

    Christopher Afeku Junior

    06/16/2022, 7:38 AM
    Also, what puppetserver — puppet agent pair are best suitable please?
  • l

    Lumiere

    06/16/2022, 1:28 PM
    the puppetserver and agent versions should match for puppet 7
  • l

    Lumiere

    06/16/2022, 1:28 PM
    (so both 7)
  • l

    Lumiere

    06/16/2022, 1:28 PM
    beyond that, they should work together ok
  • s

    Slackbot

    06/16/2022, 2:01 PM
    This message was deleted.
    n
    l
    r
    • 4
    • 3
  • y

    Yury Bushmelev

    06/16/2022, 3:19 PM
    I'm stuck a bit with
    Error: certificate verify failed [unable to get local issuer certificate for CN=xxx]
    error during
    puppet ssl bootstrap
    on a fresh VM.. what is the most obvious reason for this?
    ✔️ 1
  • y

    Yury Bushmelev

    06/16/2022, 3:19 PM
    I'm stuck a bit with
    Error: certificate verify failed [unable to get local issuer certificate for CN=xxx]
    error during
    puppet ssl bootstrap
    on a fresh VM.. what is the most obvious reason for this?
  • l

    Lumiere

    06/16/2022, 3:40 PM
    you shouldn't need to puppet ssl bootstrap?
  • l

    Lumiere

    06/16/2022, 3:40 PM
    what are you trying to do exactly?
  • y

    Yury Bushmelev

    06/16/2022, 3:48 PM
    I was debugging the
    puppet agent
    throwing the error above... the reason was
    ca_port
    pointing to compile master port facepalm
  • l

    Lumiere

    06/16/2022, 3:52 PM
    ah, yea generally I just puppet agent -t and let it run, but yea that'd do it
  • l

    Lumiere

    06/16/2022, 3:53 PM
    I use srv_domain at this point so I just tell it what the puppet srv record base is and it figures it all out (use_srv_records and srv_domain)
  • n

    natemccurdy

    06/16/2022, 4:04 PM
    puppet agent -t --http_debug
    can help in those cases as it will show the <endpoint>:<port> connections being made each step of the way.
  • p

    Peter

    06/16/2022, 5:42 PM
    Hey everyone, I have question about puppet and docker. The benefits of puppet are many, but among them is, given a properly written module from the forge, for example, Apache or Nginx, the configurations are created for me. This makes sense when I’m using a server or an EC2 instance because I can install the agent. However, when using docker, I am running only the nginx or apache daemon inside. There is no agent. Is there any best practices or established ways of getting the benefits of Puppet in docker containers?
  • l

    Lumiere

    06/16/2022, 6:26 PM
    you could use puppet apply to install the daemon and its configuration, (possibly via a mount during build?) you likely could make the aio agent available as a mount if you were just doing apply as well
  • l

    Lumiere

    06/16/2022, 6:26 PM
    then the actual container wouldn't contain anything (I don't have containers in my puppet configs at this point)
  • p

    Peter

    06/16/2022, 7:04 PM
    The usual thing puppet handles in a conventional machine don't exist in a container. There is no “service”. In a container, you're running a process (which may be the service itself). And usually the process id of it is 1. This shows that's the first thing to run in the container. Although some light research showed this: https://puppet.com/blog/running-puppet-software-docker-containers/
  • p

    Peter

    06/16/2022, 7:04 PM
    It's still not quite right because it treats containers like they're conventional systems.
  • p

    Peter

    06/16/2022, 7:05 PM
    But maybe this is an immutable compromise.
  • n

    natemccurdy

    06/16/2022, 7:05 PM
    In a Puppet+Docker/Container world, I’ve found that a good model is to use Puppet during the image build process, not during the container runtime process.
  • p

    Peter

    06/16/2022, 7:06 PM
    The usual thing puppet handles in a conventional machine don't exist in a container. There is no “service”. In a container, you're running a process (which may be the service itself). And usually the process id of it is 1. This shows that's the first thing to run in the container. Although some light research showed this: https://puppet.com/blog/running-puppet-software-docker-containers/
  • p

    Peter

    06/16/2022, 7:06 PM
    It's seems that's the only real option.
  • p

    Peter

    06/16/2022, 7:07 PM
    Unless you install something like supervisord in the container and let it manage the puppet agent process and whatever your app may be.
  • p

    Peter

    06/16/2022, 7:10 PM
    What I especially like about the puppet agent is for instance with Nginx, I can change the number of workers by calculating how much memory there is.
  • p

    Peter

    06/16/2022, 7:10 PM
    I can't do that if I don't have a running agent.
  • l

    Lumiere

    06/16/2022, 7:11 PM
    yes, but you could do that via a startup script, or building the image based on knowing what containers will be built
  • k

    khudson

    06/16/2022, 7:11 PM
    i don't like containers
1...656667...428Latest