Public | Automated Build

Last pushed: 4 months ago
Short Description
Container ready to run Pentaho BI Server 5.4
Full Description

Pentaho-BI container

Pentaho BI Community Edition container, with helper script to configure the Pentaho environment to use mysql as the repository.

To build the container:

git clone
cd docker-pentaho-env

# To build the x86 version
docker build -t pentaho-env .

To run:

docker run --rm -p 8080:8080 \
           -v /opt/pentaho/biserver-ce:/opt/biserver-ce \
           --name pentaho pentaho-env

The container exposes port 8080.


Pentaho runs from directory /opt/biserver-ce. You must:

  • Download the Pentaho Business Analytics Platform - Community Edition software from
  • Unzip it somewhere in your host server, say /opt/pentaho
  • Mount the resulting /opt/pentaho/biserver-ce folder to the container, in the /opt/biserver-ce path.

The container provides the standalone node for CDC already running, for the benefit of your CDC.


The container includes a helper script to help configure the Pentaho installation to connect to the MySQL repository. Run the command /opt/ inside the container, providing the following four parameters:

  • MySQL server name
  • MySQL server port
  • Prefix to add to the databases, to make the names unique
  • Password for the quartz and jackrabbit users

e.g, run:

docker run --rm -it -v /opt/pentaho/biserver-ce:/opt/biserver-ce pentaho-env \
    /opt/ 3306 prefix_ MySecret1234 > script.sql

The output of this command is the set of SQL statements to run in the database, in order to create the required schemas, users and passwords.

Environment variables

If Pentaho is to be run behind a reverse proxy, two environment variables must be provided:

  • PROXY_PORT: port number of the proxy, defualt 80.
  • PROXY_SCHEME: scheme used by the proxy, default http.

Typically, if deploying behind a ssl proxy, the values of these environment variables should be:

  • PROXY_PORT=443
  • PROXY_SCHEME=https


If you run Pentaho behind a reverse HTTPS proxy, it will not be able to get the right schema from the URL, and some .jsp files will incorrectly render links to external resources using http:// instead of https://. This yields errors in some browsers.

To fix this, you may need to edit the .jsp files where those links are generated, and set the schema to https by hand. The affected files are:

  • tomcat/webapps/pentaho/mantle/home/index.jsp: look for BrightcoveExperiences.js


The default Pentaho config misses a few opportunities for optimizations:

  • Enable server mode for the JVM by adding the flag -server to the JVM commandline at tomcat/bin/
  • Set the heap initial and maximum size at the same file.
  • Disable Audit Logging by replacing the IAuditEntry bean at ./pentaho-solutions/system/pentahoObjects.spring.xml with the following bean:
<bean id="IAuditEntry" class="org.pentaho.platform.engine.core.audit.NullAuditEntry" scope="singleton" />
  • Since this is a docker container, logs are better sent to the console instead of a file. To change the logging settings,

    • Remove the references to the PENTAHOFILE appender at tomcat/webapps/pentaho/WEB-INF/classes/log4j.xml
    • Change the logging levels at pentaho-solutions/system/cda/log4j.xmla
    • Leave only one handler at the .handlers stanza of tomcat/
.handlers = java.util.logging.ConsoleHandler
  • Improve the configuration of the tomcat Connector at tomcat/conf/server.xml:

    • Uncomment the tomcatThreadPool Executor tag and add the executor="tomcatThreadPool" attribute to the Connector tag. 200 threads per CPU is the suggested configuration for the Executor.
    • If your installation must support keepalives, replace the blocking BIO scheduler by the native APR one, adding the attribute protocol="org.apache.coyote.http11.Http11AprProtocol" to the Connector tag.

      • Notice that if there are no keepalives, even in the face of high concurrency, the BIO scheduler (protocol="HTTP/1.1") is preferred.
      • If that's the case, disable keepalives altogether with the maxKeepAliveRequests=1 attribute.
    • Disable DNS lookups by adding the attribute enableLookups=false" to the Connector tag.

Caching with CDC

You can install the Community Distributed Cache from the marketplace to improve caching control (allows you to clean the CDA cache of a single dashboard, selectively).

Once the plugin is installed, you may need to manually copy the files from solution/system/cdc/pentaho-lib to tomcat/webapps/pentaho/WEB-INF/lib, and reboot the server.

For your convenience, this container includes the standalone node for CDC already running, so CDC should be up and running as soon as you install it.

Docker Pull Command
Source Repository

Comments (0)