Skip to content
Docker image for LibreNMS
Branch: master
Clone or download
Latest commit b043b58 May 28, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
files baseimage-librenms 2.5 (php 7.3), replace composer with git clone Mar 7, 2019
.gitignore gitignore Dec 9, 2016
Dockerfile librenms 1.52 May 28, 2019
LICENSE nginx 1.9.3 and disabled autoupdate Aug 17, 2015
MYSQL.md mysql docs Apr 1, 2017
README.md
docker-compose.yml Un-exposed 3306 to host and improved composition Nov 14, 2018

README.md

docker-librenms

Docker image for LibreNMS

This document refers to the master branch and does not necessarily correspond to the version that you are running. It is recommended to extract the readme from your preferred release's source code archive. Releases are listed on the Releases page.

About

This is a generic docker container for LibreNMS.

The container runs nginx 1.15+ with HTTP/2 support and PHP 7.3 FPM with OPCache and rrdcached for maximum performance.

Initial setup

Database - Prerequisites

If you don't have a MySQL server setup either in Docker or elsewhere then you can create a docker container here.

You should read the LibreNMS installation docs for the latest instructions regarding database setup.

As of November 2016, the following is still a requirement:

NOTE: Whilst we are working on ensuring LibreNMS is compatible with MySQL strict mode, for now, please disable this after mysql is installed.

Generating an encryption key

You must first generate a unique encryption key.

Generating the key

docker run --rm jarischaefer/docker-librenms generate_key

Output example

base64:Q0+ZV56/5Uwz79vsvS4ZfwQFOty3e9DJEouEy+IXvz8=

Make sure you keep the key secret, because anyone in possession of it can decrypt sensitive data.

The key (including base64:) must be passed via the APP_KEY environment variable in the docker run command.

Database - Creating LibreNMS tables

You should have a MySQL server running at this point. Make sure the database, user and permissions exist before running the commands.

Next, follow the instructions for running the container. Once the container is up and running, you may use the following commands to populate the database and create an admin user.

Creating the tables

docker exec librenms setup_database

Creating an initial admin user

docker exec librenms create_admin
  • User: admin
  • Password: admin

Running the container

The examples below do not cover all of the available configuration options, check the appropriate section in the docs for a complete list.

Linked database container

In the example below the linked container is named my-database-container and its alias inside the container is db. Make sure my-database-container matches the MySQL container's name and DB_HOST matches its alias inside the container if you intend to modify it.

docker run \
	-d \
	-h librenms \
	-p 80:80 \
	-e APP_KEY=the_secret_key_you_have_generated \
	-e DB_HOST=db \
	-e DB_NAME=librenms \
	-e DB_USER=librenms \
	-e DB_PASS=secret \
	-e BASE_URL=http://localhost \
	--link my-database-container:db \
	-v /data/logs:/opt/librenms/logs \
	-v /data/rrd:/opt/librenms/rrd \
	--name librenms \
	jarischaefer/docker-librenms

Remote database

docker run \
	-d \
	-h librenms \
	-p 80:80 \
	-e APP_KEY=the_secret_key_you_have_generated \
	-e DB_HOST=x.x.x.x \
	-e DB_NAME=librenms \
	-e DB_USER=librenms \
	-e DB_PASS=secret \
	-e BASE_URL=http://localhost \
	-v /data/logs:/opt/librenms/logs \
	-v /data/rrd:/opt/librenms/rrd \
	--name librenms \
	jarischaefer/docker-librenms

Updating the container

Pulling a new version

  1. Pick a release from the Releases page
  2. Run docker pull jarischaefer/docker-librenms:{release}
  3. Restart your container using the new version
  4. Follow the steps for database updates

Manual database updates (safe)

Run docker exec librenms setup_database.

Automatic database updates (potentially unsafe)

If you would like to update the database automatically on startup, you may pass DAILY_ON_STARTUP=true. Keep in mind that restarting more than one container simultaneously could result in concurrency issues and damage your database.

The LibreNMS implementation (as of October 2018) uses a distributed lock via memcache to avoid this scenario. Therefore, if all containers share the same memcache instance, concurrent restarts would be safe.

SSL

Mount another directory containing ssl.key, ssl.crt and optionally ssl.ocsp.crt to enable HTTPS. You'll also have to change BASE_URL.

docker run \
	-d \
	-h librenms \
	-p 80:80 \
	-p 443:443 \
	-e APP_KEY=the_secret_key_you_have_generated \
	-e DB_HOST=db \
	-e DB_NAME=librenms \
	-e DB_USER=librenms \
	-e DB_PASS=secret \
	-e BASE_URL=https://localhost \
	--link my-database-container:db \
	-v /data/logs:/opt/librenms/logs \
	-v /data/rrd:/opt/librenms/rrd \
	-v /data/ssl:/etc/nginx/ssl:ro \
	--name librenms \
	jarischaefer/docker-librenms

Environment config

The following keys can be passed directly via the -e switch:

Basic configuration

Key Default Description
APP_KEY Secret encryption key
APP_KEY_FILE Secret encryption key via file/secret
BASE_URL Base URL for LibreNMS (e.g. http://192.168.0.1:8080)
DB_HOST MySQL IP or hostname
DB_PORT 3306 MySQL port
DB_NAME MySQL database name
DB_USER MySQL user
DB_PASS MySQL password
DB_PASS_FILE MySQL password via secret
TZ UTC Timezone (e.g. Europe/Zurich)

Enabling/disabling container features

Key Default Description
DISABLE_IPV6 false Disable nginx IPv6 socket
MEMCACHED_ENABLE false Enable memcached
MEMCACHED_HOST memcached IP or hostname
MEMCACHED_PORT 11211 memcached port
NGINX_ENABLE true Enable nginx
PHPFPM_ENABLE true Enable PHP-FPM
RRDCACHED_ENABLE true Enable rrdcached
RRDCACHED_CONNECT unix:/var/run/rrdcached/rrdcached.sock rrdcached TCP or unix socket where LibreNMS connects to
RRDCACHED_LISTEN unix:/var/run/rrdcached/rrdcached.sock rrdcached TCP or unix socket where rrdcached listens on
SKIP_CHOWN false Disable (slow) chowning of files at startup (might help with network storage)

Enabling/disabling LibreNMS features

Key Default Description
ALERTS_ENABLE true Enable LibreNMS alerts
BILLING_CALCULATE_ENABLE true Enable LibreNMS billing calculation
CHECK_SERVICES_ENABLE true Enable LibreNMS service checks
DAILY_ENABLE true Enable LibreNMS daily script
DAILY_ON_STARTUP false Enable LibreNMS daily script on startup
DISCOVERY_ENABLE true Enable LibreNMS discovery
DISCOVERY_THREADS 1 Number of threads for discovery
ENABLE_SYSLOG false Enable LibreNMS syslog (see here)
POLL_BILLING_ENABLE true Enable LibreNMS billing polling
POLLERS_ENABLE true Enable LibreNMS polling
POLLERS 8 Number of LibreNMS pollers
POLLERS_CRON */5 * * * * Cron schedule for pollers
SNMP_SCAN_ENABLE false Enable cron for snmp-scan
SNMP_SCAN_CRON 0 0 * * * Cron schedule for snmp-scan
WEATHERMAP_ENABLE false Enable cron for weathermap (see here)
WEATHERMAP_CRON */5 * * * * Cron schedule for weathermap

syslog

These are instructions for the LibreNMS syslog extension.

  • Add -e ENABLE_SYSLOG=true to your docker run command
  • Add -p 514:514 and -p 514:514/udp to your docker run command
  • Configure the remote host whose logs should be gathered (rsyslog example)
    • Create /etc/rsyslog.d/60-librenms.conf
    • Add *.* @example.com:514

Weathermap

These are instructions for the LibreNMS weathermap plugin.

The weathermap plugin requires additional mounts to persist its data.

  • /opt/librenms/html/plugins/Weathermap/configs for the configs
  • /opt/librenms/html/plugins/Weathermap/output for the generated data

Make sure you set Output Image Filename to output/example.png and Output HTML Filename to output/example.html in the Map Properties configuration section so the files are persisted in the output directory.

Custom config

You may apply custom configuration by mounting files matching *.php in /opt/librenms/conf.d.

In the example below /data/config.interfaces.php on the host is mounted inside the container at /opt/librenms/conf.d/config.interfaces.php.

docker run \
	-d \
	-h librenms \
	-p 80:80 \
	-p 443:443 \
	-e APP_KEY=the_secret_key_you_have_generated \
	-e DB_HOST=db \
	-e DB_NAME=librenms \
	-e DB_USER=librenms \
	-e DB_PASS=secret \
	-e BASE_URL=https://localhost \
	--link my-database-container:db \
	-v /data/logs:/opt/librenms/logs \
	-v /data/rrd:/opt/librenms/rrd \
	-v /data/ssl:/etc/nginx/ssl:ro \
	-v /data/config.interfaces.php:/opt/librenms/conf.d/config.interfaces.php \
	--name librenms \
	jarischaefer/docker-librenms

config.interfaces.php

<?php

$config['bad_if_regexp'][] = '/^docker[-\w].*$/';
$config['bad_if_regexp'][] = '/^lxcbr[0-9]+$/';
$config['bad_if_regexp'][] = '/^veth.*$/';
$config['bad_if_regexp'][] = '/^virbr.*$/';
$config['bad_if_regexp'][] = '/^lo$/';
$config['bad_if_regexp'][] = '/^macvtap.*$/';
$config['bad_if_regexp'][] = '/gre.*$/';
$config['bad_if_regexp'][] = '/tun[0-9]+$/';

Disabling cron jobs or the local rrdcached instance

If you plan to use this container for a distributed LibreNMS installation, you may want to disable some of the default cron jobs, or the local rrdcached, nginx and php-fpm services. You could also increase the number of discovery-wrapper.py threads.

docker run \
	-d \
	-h librenms \
	-p 80:80 \
	-e APP_KEY=the_secret_key_you_have_generated \
	-e DB_HOST=db \
	-e DB_NAME=librenms \
	-e DB_USER=librenms \
	-e DB_PASS=secret \
	-e BASE_URL=http://localhost \
	-e POLLERS=16 \
	-e TZ=UTC \
	-e DISCOVERY_THREADS=2 \
	-e DAILY_ENABLE=false \
	-e ALERTS_ENABLE=false \
	-e CHECK_SERVICES_ENABLE=false \
	-e RRDCACHED_ENABLE=false \
	-e NGINX_ENABLE=false \
	-e PHPFPM_ENABLE=false \
	--link my-database-container:db \
	-v /data/logs:/opt/librenms/logs \
	-v /data/rrd:/opt/librenms/rrd \
	--name librenms \
	jarischaefer/docker-librenms

Executing commands inside the container

Make sure you source the environment variables from /etc/librenms_environment prior to executing commands inside the container.

This is an example demonstrating how to run the validation script.

su - librenms
source /etc/librenms_environment
cd /opt/librenms
php validate.php

Running in production

The commands above are purely for illustrative purposes. You should customize them to fit your environment.

Also, please note that...

  • Alerting via email is supported via SMTP only.
  • Publicly accessible installations should be put behind jwilder/nginx-proxy or similar proxies for better access control and security hardening.

License

This project is open-sourced software licensed under the MIT license.

LibreNMS has its own license, this license only covers the Docker part.

You can’t perform that action at this time.