webdetails / cbf2 Goto Github PK

Thank you for this great docker bundle. A few weeks back it started failing to pull down. My original guess was that 1 of the layers that "Already exists" was the problem. I also received the "layers from manifest don't match image configuration" message after removing all images and containers. Below is a recent attempt with some layers which already exist

OS= Mac OSX 10.10.5
Docker=Version 1.12.0-rc2-beta17 (build: 9779)

$ docker pull pentaho/biserver
Using default tag: latest
latest: Pulling from pentaho/biserver
6ffe5d2d6a97: Already exists
f4e00f994fd4: Already exists
e99f3d1fc87b: Already exists
a3ed95caeb02: Pull complete
b3598f593928: Pull complete
02c26cc5a15d: Pull complete
99eaa6b2bdf3: Pull complete
04af1d27b3f2: Pull complete
e994be9c77bf: Pull complete
a8d0724e4356: Pull complete
f7509f7e0b67: Pull complete
b64162ceb76a: Pull complete
bb170c8d35f6: Pull complete
ed31c6d56223: Pull complete
9d0bac0300fc: Pull complete
8434f018e234: Pull complete
layers from manifest don't match image configuration

Regards

EE image builds with patching appears to be from a different time and place.
Patches from Hitachi Vantara Pentaho now are only .bin files. A ticket to professional support resulted in a suggestion to

PentahoServer-SP-${product.version}.exe -i silent -DEULA_ACCEPT=true -DMANUAL_PATCH_PATH=/tmp/dump -DSILENT_LOG=/tmp/pentaho-installer.log -DSOURCE_VERSION=8.0.0.0-28

-DSILENT_LOG is optional and will give a legible explanation of the execution's result
-DMANUAL_PATCH_PATH must already exist
-DSOURCE_VERSION is the version of the product to be patched.

Exit Codes:
See Silent installation section above

The patches do not extract to the destination specified, but rather /tmp/patch name.
The existing shell script used to look for BIServer within the patch, but does that would not exist anymore due to the new structure.

The 'processing' part of the patch also does not work anymore, for reasons I haven't traced yet.

Finally the image produced retains the old / base version 8.0.0.0-28 after patching. Not sure if that is a symptom of failed patching or just a get to it later feature.

Hitachi Vantara Pentaho crews seem to enjoy 'zip' builds that include patches and are distributed as blah-dist.zip's. Nevermind, customers like me have asked for ages, and it did not come to fruition. So this fact probably plays into the neglect of this functionality.

Hello

I had problems creating volumes using cbf2.

Even adding the script "dockerVolumes.sh" in the "config" directory within my project did not obitive success with creating the volumes.

When checking the script "cbf2.sh" I noticed that the method that identifies the project name is causing the failure when the name contains a hyphen character "-".

Line 225
"projectName=$(echo $build | egrep 'pdu-' | cut -d' ' -f 1 | cut -d'-' -f 2)"

This also happens in the example project "horlogery-demo".
The mentioned method identifies the project name as "horlogery" instead of "horlogery-demo" causing the location of the "dockerVolumes.sh" script directory not to be located.

If you like to build images on MacOS look at the fork
https://github.com/omski/cbf2

box.com does not allow FTP access on free tier accounts so I added a hint where to download install binaries from sourceforge.net manually

Substituir o oracle-java8-installer por openjdk-8-jdk no arquivo cbf2/dockerfiles/Dockerfile-CoreCBF

Hello,

I google around to find out a way to run Pentaho BI server in docker, but all solutions out there seems obsoleted and cannot work ...
I found this one, but example here is about BI server up to version 6, afaik, there is a big change in version 7 of BI server ... Now, the latest version of BI server is 8.0 CE, is it possible for me to use cbf2 to build and run BI server in docker?

Thanks.

BOX_USER and BOX_PASS are set, but I keep getting Login failed: 530 Box: Missing parameters. "username" and "password" required..