You can install the RPM on /opt folder and re-use the same installation on
multiple systems.
Just be sure to configure puppet agent to not store node specific information
in /opt.
Check config options by running "sudo puppet config print —all” after Puppet
agent installation
Hth,
Martin
>
Could you cheat and create /opt2/puppetlabs and a symlink
from /opt/puppetlabs -> /opt2/puppetlabs before installation?
Otherwise, you can likely unpack the rpm, and futz with it,
but I could imagine that /opt/puppetlabs is buried in a
binary or two and thus awkward to change.
Hope that helps -
Ah, you need the whole thing to be relocatable!
Yeah, that's much more difficult, even with a SRPM to be honest depending
on how the components are built.
I think that it's configurable in Vanagon so you can probably build the
container image, hop into it and dig around to see where you might
Thank you! Unfortunately that won't work for me. The issue I have is
due to /opt is some NFS read-only mounts. I am wondering about how to
get a new RPM created for puppet-agent6, so that it could be installed
on some folder like /opt2 instead. Right now I could not install this
rpm. The other
This community hosted project contains dockerfiles that outline the steps
required for building from source
https://github.com/simp/releng-misc/tree/master/puppet_agent_build
On Mon, Apr 20, 2020 at 2:22 PM Morgan Rhodes wrote:
> Hi,
>
> We no longer provide source RPMs for puppet6 packages due
Hi,
We no longer provide source RPMs for puppet6 packages due to lack of
support from the packaging tools we use.
On Sat, Apr 18, 2020 at 1:28 PM hai wu wrote:
> Where is source rpm for puppet6 open source rpms? I could not find them ..
>
> --
> You received this message because you are
Where is source rpm for puppet6 open source rpms? I could not find them ..
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
