Setting up your machine

If you ever get stuck during this installation, be sure to reboot the machine once. It may help to correctly load some configurations and/or daemons.

The tool requires a linux distribution as foundation, a webserver (instructions only given for NGINX, but any webserver will do), python3 including some packages, and docker installed (rootless optional). In this manual we are assuming you are running a Debian/ Ubuntu flavour of Linux.

We recommend to fully reset the node after every run, so no data from the previous run remains in memory or on disk.

git clone /var/www/green-metrics-tool && \
sudo apt update && \
sudo apt upgrade -y && \
sudo apt install make gcc python3 python3-pip libpq-dev -y && \
sudo pip3 install psycopg2 pandas pyyaml

The sudo in the last command is very important, as it will tell pip to install to /usr directory instead to the home directory. So we can find the package later with other users on the system. If you do not want that use a venv in Python.


Docker provides a great installation help on their website that will probably be more up to date than this readme:

However, we provide here what we used in on our Ubuntu system, but be sure to double check on the official website. Especially if you are not running Ubuntu.

Base install

curl -fsSL | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg && \
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null && \
sudo apt update && \
sudo apt remove docker docker-engine containerd runc -y && \
sudo apt install ca-certificates curl gnupg lsb-release -y && \
sudo apt install docker-ce docker-ce-cli docker-compose-plugin -y

You can check if everything is working fine by running docker stats. It should connect to the docker daemon and output a view with container-id, name, and stats, which should all be empty for now.

Rootless mode

The Green Metrics Tool is currently designed to work only with Docker in rootless mode.

If your docker daemon currently does not run in rootless mode please follow the heregiven instructions.

In order to use rootless mode you must have a non-root user on your system (see

👉 Typically a normal installation of ubuntu has at least one non-root user setup during installation.

Important: If you have just created a non root user be sure to relog into your system (either through relogging, or a new ssh login) with the non-root user. A switch with just su my_user will not work.

The docker-ce-rootless-extras package on Ubuntu provides a script, which must be installed and run:

sudo systemctl disable --now docker.service docker.socket && \
sudo apt install uidmap && \
sudo apt update && \
sudo apt-get install -y docker-ce-rootless-extras dbus-user-session && \ install

After the installation the install script will tell you to add some export statements to your .bashrc file. Please do so to always have the correct paths referenced if you open a new terminal.

Lastly please run the following commands to have the docker daemon always lingering:

systemctl --user enable docker
sudo loginctl enable-linger $(whoami)

You must also enable the cgroup2 support with the metrics granted for the user:

Make sure to also enable the CPU, CPUSET, and I/O delegation as instructed there.


The Dockerfiles will provide you with a running setup of the working system with just a few commands.

It can technically be used in production, however it is designed to run on your local machine for testing purposes.

The system binds in your host OS to port 8000. So the web view will be accessible through


Please run the script in the root folder.

This script will:

  • Set the database password for the containers
    • By default the script will ask you to provide a password, but you can also pass it in directly with the -p parameter.
  • Create the needed /etc/hosts entries for development
  • Build the binaries for the Metric Providers

What you might want to add:

  • SMTP mail sending is by default deactived, so for a quick-start you do not have to change that in the config.yml
  • The RAPL reporter is by default deactived. Please check the Metric Providers Documentation on how to active it

After that you can start the containers:

  • Build and run in the docker directory with docker compose up
  • The compose file uses volumes to persist the state of the database even between rebuilds. If you want a fresh start use: docker compose down -v && docker compose up
  • To start in detached mode just use docker compose -d

Connecting to DB

You can now connect to the db directly on port 5432, which is exposed to your host system.
This exposure is not strictly needed for the green metrics tool to run, but is useful if you want to access the db directly. If you do not wish to do so, just remove the 5432:5432 entry in the compose.yml file.

The database name is green-coding, user is postgres, and the password is what you have specified during the run, and can be found in the compose.yml file.

Restarting Docker containers on system reboot

We recommend systemd. Please use the following service file and change the USERNAME and GROUPNAME accordingly to the ones on your system.

The file will be installed to: /etc/systemd/system/green-coding-service.service

Description=Docker Compose for all our services



As you can see Restart is set to never. The reason is that the docker dameon will restart the containers by itself. The systemd script is only needed to start the container once on reboot.

As you can see we also reference the /home/USERNAME/ file which systemd expects to be in your home directory.

Please create the following file in your home directory and change PATH_TO_GREEN_METRICS_TOOL accordingly:

docker context use rootless
docker compose -f PATH_TO_GREEN_METRICS_TOOL/docker/compose.yml up -d

Dockerfiles architecture explanation:

  • The postgres container has a volume mount. This means that data in the database will persists between container removals / restarts
  • The interconnect between the gunicorn and the nginx container runs through a shared volume mount in the filesystem. Both use the user www-data to read and write to a UNIX socket in /tmp
  • all webserver configuration files are mounted on start of the container as read-only. This allows for changing configuration of the server through git-pull or manual editing without having to rebuild the docker image.
  • postgresql can detect changes to the structure.sql. If you issue a docker compose down -v the attached volume will be cleared and the postgres container will import the database structure fresh.

Metric providers

Some metric providers need extra setup before they work.


Install the required libraries to read the temperature metrics:

sudo apt install lm-sensors libsensors-dev libglib2.0-0 libglib2.0-dev

If you want the temperature metric provider to work you need to run the sensor detector

sudo sensors-detect

in order to detect all the sensors in your system. One you have run this you should be able to run the


command and see your CPU temp. You can then use this output to look for the parameters you need to set in the config.yml. For example if sensors gives you:

Adapter: ISA adapter
Package id 0:  +29.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +27.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +27.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +28.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +29.0°C  (high = +100.0°C, crit = +100.0°C)

Your config could be:

    resolution: 100
    chips: ['coretemp-isa-0000']
    features: ['Package id 0', 'Core 0', 'Core 1', 'Core 2', 'Core 3']

As the matching is open ended you could also only use 'Core' instead of naming each feature.


The XGBoost metrics provider can estimate the power consumption of the total system (AC-Energy).

It is included as a submodule in the Green Metrics Tool and must be separately checked out via:

git submodule update --init

It must be supplied with the machine params in the config.yml file:

  • CPUChips
  • HW_CPUFreq
  • CPUCores
  • TDP
  • HW_MemAmountGB

Please look at the always current documentation here to understand what values to plug in here: XGBoost SPECPower Model documentation

Also the model must be activated by uncommenting the appropriate line with …PsuEnergyXgboostSystemProvider

Lastly, if you don’t have them already, you need to install some python libraries:

python3 -m pip install xgboost statsmodels scipy numpy pandas scikit-learn

DC Metrics Provider

This providers needs a custom piece of hardware to work:

Please look for details in the provider documentation at PsuEnergyDcSystemProvider →


On kernels > 2.6 all the kernel modules should automatically be loaded.

However just in case run:

sudo modprobe intel_rapl_common # or intel_rapl for kernels < 5
sudo modprobe intel_rapl_msr
sudo modprobe rapl


ℹ️ If you just want to run the Green Metrics Tool manually the cronjob is not needed.
ℹ️ It is only to have it pick up jobs entered through the web interface when it is running autonomous on a testing server.

The Green Metrics Tool comes with an implemented queuing and locking mechanism.

You can install a cronjob on your system to periodically call:

  • python3 PATH_TO_GREEN_METRICS_TOOL/tools/ project to measure projects in database queue
  • python3 PATH_TO_GREEN_METRICS_TOOL/tools/ email to send all emails in the database queue

The uses the python3 faulthandler mechanism and will also report to STDERR in case of a segfault. When running the cronjob we advice you to append all the output combined to a log file like so: * * * * * python3 PATH_TO_GREEN_METRICS_TOOL/tools/ project &>> /var/log/green-metrics-jobs.log

Be sure to give the green-metrics-jobs.log file write access rights.

Also be aware that our example for the cronjob assumes your crontab is using bash. Consider adding SHELL=/bin/bash to your crontab if that is not the case.