Hi Konstantin, I see your point. My goal however was to generate RPMs for some projects (Spark particularly) and experiment with different versions and configurations.
I could not find a proper doc explaining how to bootstrap with Bigtop. The wiki pages like ( https://cwiki.apache.org/confluence/display/BIGTOP/Building+Bigtop+on+RHEL7) are outdated, missing libraries and stil refering to the 'make' tool. I've tried the './gradlew toolchain' to build an environment but it still requires some libs to be preinstalled so i've decided to keep everything in a single Dockerfile. Concerning only the packaging tasks I guess 2 environments (for RPM and DEB) are enough? Cheers, Christian On Mon, Feb 23, 2015 at 8:39 PM, Konstantin Boudnik <[email protected]> wrote: > Thanks Christian. > > We have considered this on a multiple occasions and as you found for > yourself > the Dockerfile file is pretty simple, so the consensus was to just > check-in a > Gradle code for its generation, hence making containers preparation as > stateless as possible. > > Roman should have this patch somewhere, not sure if he's ready to commit > yet. > But we always can use your approach is a backup plan, although we'd need > Dockerfiles for all supported Linuxes. > > Cos > > On Mon, Feb 23, 2015 at 07:45PM, Christian Tzolov wrote: > > I've put together a Docker container, equipped with all necessary > tools > > and libraries and ready to generate RPM packages. Here are the > > Dockerhub/Github references: > > https://registry.hub.docker.com/u/tzolov/bigtop-centos > > https://github.com/tzolov/bigtop-centos > > There are a couple of existing bigtop images in Dockerhub but neither > of > > them provides neither description nor a Dockerfile. > > > > For simplicity I've decided to keep it as as single image for now. > > Cheers, > > Christian >
