> some time ago I created simple Foreman appliance which was based on
> Fedora and it was running a simple git checkout.
> I'd like to push this a step further and create new CentOS based image
> with Foreman installed from RPM using our installer. The goal is to have
> Foreman app installed and run it via webrick (foreman-rake server). To
> get there, I need to solve one issue with the installer.
Why diverging from the default Apache + passenger setup we have in other places?
> When building a docker image, the environment has hostname set to
> container id (sha, or whatever this is called in docker terms):
> # hostname
> This of course breaks our installer since we expect FQDN because of
> Now, is there any way to configure our installer to skip all the
> FQDN-dependant puppet tasks? I am not interested in smart proxy and
> services, I am only interested in Foreman itself (plus the ENC script).
> If this is not possible, can Puppet experts give me some overview what
> needs to be done to allow this?
I don't consider myself a Puppet expert, but I would expect we would need
to have some variable ($skip_finish, or something like that), that wouldn't
- generate the certificates
- start and enable the services
This would be useful not just for docker images, but other images as well.
> Then, once container is executed with proper hostname set (via docker -h
> option), we can execute the installer for the 2nd time to finish the
> installation which should be relatively fast as everything should be
> already set up.
> Opinions? Anyone interested?
I was looking at possibilities for Katello as well (what a synchronization),
and awaiteka from pulp team was already doing some work around pulp:
https://github.com/aweiteka/pulp-dockerfiles - might be interesting place
Being able to run foreman, pulp, candlepin, puppet and smart proxy in containers
would be really nice for development (especially when more things testing
in parallel). From this perspective, being able to run the other services
that Foreman/Katello needs is more interesting for me, than the foreman itself
(although, for running the foreman on the stack we package it's definitely big win)
----- Original Message -----
Lukas #lzap Zapletal
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an
email to email@example.com.
For more options, visit https://groups.google.com/d/optout.