Public | Automated Build

Last pushed: 5 days ago
Short Description
A dockerized Promet GUI Client
Full Description

A dockerized Variant of Promet-ERP

Persist Data
docker run --publish 10088:8080 --volume /my-docker-data-dir/promet:/srv/promet promet-client


Dockerfile to run Promet-ERP promet-ERP GUI Client from an container image.


If you find this image useful here's how you can help:

  • Send a Pull Request with your awesome new features and bug fixes
  • Be a part of the community and help resolve Issues


Docker is a relatively new project and is active being developed and tested by a thriving community of developers and testers and every release of docker features many enhancements and bugfixes.

Given the nature of the development and release cycle it is very important that you have the latest version of docker installed because any issue that you encounter might have already been fixed with a newer docker release.

Install the most recent version of the Docker Engine for your platform using the official Docker releases, which can also be installed using:

wget -qO- | sh

Fedora and RHEL/CentOS users should try disabling selinux with setenforce 0 and check if resolves the issue. If it does than there is not much that I can help you with. You can either stick with selinux disabled (not recommended by redhat) or switch to using ubuntu.

You may also set DEBUG=true to enable debugging of the entrypoint script, which could help you pin point any configuration issues.

If using the latest docker version and/or disabling selinux does not fix the issue then please file a issue request on the issues page.

In your issue report please make sure you provide the following information:

  • The host distribution and release version.
  • Output of the docker version command
  • Output of the docker info command
  • The docker run command you used to run the image (mask out the sensitive bits).


Your docker host needs to have 300MB or more of available RAM to run Promet-ERP.


Automated builds of the image are available on Dockerhub and is the recommended method of installation.

docker pull cutec/promet-client:latest

Alternatively you can build the image locally.

docker build -t cutec/promet-client

Quick Start

Step 1. Launch the promet container

docker run --publish 10088:8080 cutec/promet-client

Point your browser to http://localhost:10088 and go through the Mandant Wizard to create and Database and prefill it with an Profile.

You should now have the Promet-ERP application up and ready for testing. If you want to use this image in production then please read on.


Data Store

promet-ERP is an (Article,Contact,Project,Document) Management Software and as such you don't want to lose your Data when the docker container is stopped/deleted. To avoid losing any data, you should mount a volume at,

  • /srv/promet

SELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.

mkdir -p /srv/docker/promet
sudo chcon -Rt svirt_sandbox_file_t /srv/docker/promet

Volumes can be mounted in docker by specifying the -v option in the docker run command.

docker run --name promet-erp -d \
    --publish 10088:8080 \
    --volume /srv/docker/promet:/srv/promet \


Promet-ERP uses a database backend to store its data. You can configure this image to use either SQLite, MySQL, Firebird, MsSQL or PostgreSQL.


External PostgreSQL Server

The image also supports using an external PostgreSQL Server.

CREATE DATABASE promet_production;
GRANT ALL PRIVILEGES ON DATABASE promet_production to promet;

We are now ready to start the GitLab application.

Assuming that the PostgreSQL server host is

docker run --name gitlab -d \
    --publish 10088:8080 \
    --volume /srv/docker/promet:/srv/promet \


Available Configuration Parameters

Please refer the docker run command options for the --env-file flag where you can specify all required environment variables in a single file. This will save you from writing a potentially long docker run command. Alternatively you can use docker-compose.

Below is the complete list of available options that can be used to customize your gitlab installation.

Parameter Description
DB_ADAPTER The database type. Possible values: mysql2, postgresql. Defaults to postgresql.
DB_ENCODING The database encoding. For DB_ADAPTER values postresql and mysql2, this parameter defaults to unicode and utf8 respectively.
DB_HOST The database server hostname. Defaults to localhost.
DB_PORT The database server port. Defaults to 3306 for mysql and 5432 for postgresql.
DB_NAME The database database name. Defaults to gitlabhq_production
DB_USER The database database user. Defaults to root
DB_PASS The database database password. Defaults to no password
DB_POOL The database database connection pool count. Defaults to 10.


Creating backups

Restoring Backups


  • Step 1: Update the docker image.
docker pull cutec/promet-client:latest
  • Step 2: Stop and remove the currently running image
docker stop promet-erp
docker rm promet-erp
  • Step 4: Start the image
docker run --name promet-erp -d [OPTIONS] cutec/promet-client:latest

Shell Access

For debugging and maintenance purposes you may want access the containers shell. If you are using docker version 1.3.0 or higher you can access a running containers shell using docker exec command.

docker exec -it promet-erp bash


Docker Pull Command

Comments (0)