Need help with lumogon?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

199 Stars 16 Forks Other 308 Commits 6 Opened issues


Get a complete picture of what your applications are made of *without* changing how you currently build and run containers. Just run and report.

Services available


Need anything else?

Contributors list


Status Go Report Card

Lumogon provides a way to inspect, analyze and report on your running Docker containers.

Unmaintained Notice

Please note this project is no longer maintained. However, the project's code will remain open and available in this repository and the Docker Hub image will remain available.

Trying out Lumogon


| Software | Version | | ------------- |:-----------------:| | Docker | 1.13.0 or greater |

Downloading Lumogon

You'll need Docker installed and running locally. This should already be true if you have Docker containers you want to analyze with Lumogon.

docker pull puppet/lumogon

Running Lumogon

Now that you have Lumogon installed, let's run it to find out which containers you have running and what we can learn about them. The output from a Lumogon scan will be a JSON listing of all the containers found and what Lumogon could learn about them.

docker run --rm  -v /var/run/docker.sock:/var/run/docker.sock puppet/lumogon scan

After a few seconds you should see your JSON data:

  "$schema": "",
  "generated": "2017-05-09 07:59:24.287008012 +0000 UTC",
  "owner": "default",
  "group": [
  "client_version": {
    "BuildVersion": "development",
    "BuildTime": "2017-05-09 06:56:22 UTC",
    "BuildSHA": "9e8f684432ff12b04b5b5d594caa0ebcce86b844"
  "reportid": "c73a79dc-8612-4af8-8bd8-22e32ea11e38",
  "containers": {
    "5982d3f16bbbf9530ae09915b22a0d189044e3b953e5e417e2783b90de579034": {
      "$schema": "",
      "generated": "2017-05-09 07:59:03.513739277 +0000 UTC",
      "container_report_id": "8d17e541-11b3-4f25-b145-4ad9d3045995",
      "container_id": "5982d3f16bbbf9530ae09915b22a0d189044e3b953e5e417e2783b90de579034",
      "container_name": "/fixtures_alpine_1",
      "capabilities": {
        "apk": {
          "$schema": "",
          "title": "Packages (APK)",
          "type": "dockerapi",
          "harvestid": "3a5bf0d4-36d8-440b-af81-615b5493fe98",
          "payload": {
            "alpine-baselayout": "3.0.3-r0",
            "alpine-keys": "1.1-r0",
            "apk-tools": "2.6.7-r0",
            "busybox": "1.24.2-r9",
            "libc-utils": "0.7-r0",
            "libcrypto1.0": "1.0.2h-r1",
            "libssl1.0": "1.0.2h-r1",
            "musl": "1.1.14-r10",
            "musl-utils": "1.1.14-r10",
            "scanelf": "1.1.6-r0",
            "zlib": "1.2.8-r2"
        "dpkg": {
          "$schema": "",
          "title": "Packages (DPKG)",
          "type": "dockerapi",
          "harvestid": "bdee3efe-70cf-4684-9eb6-cfbfeeb96b9c"
        "host": {
          "$schema": "",
          "title": "Host Information",
          "type": "attached",
          "harvestid": "53d1961c-e8e9-4b52-8620-6bac37a69664",
          "payload": {
            "hostname": "365cfca386ec",
            "kernelversion": "4.9.21-moby",
            "os": "linux",
            "platform": "alpine",
            "platformfamily": "alpine",
            "platformversion": "3.4.0",
            "procs": "61",
            "uptime": "248396",
            "virtualizationrole": "guest",
            "virtualizationsystem": "docker"
        "label": {
          "$schema": "",
          "title": "Labels",
          "type": "dockerapi",
          "harvestid": "50a3f846-3580-4190-9b00-27c3011f1516",
          "payload": {
            "com.docker.compose.config-hash": "70e9897635135adc7e9bd0af535fef48ae8e26c8e0debbf8f40e0d67938a9884",
            "com.docker.compose.container-number": "1",
            "com.docker.compose.oneoff": "False",
            "com.docker.compose.project": "fixtures",
            "com.docker.compose.service": "alpine",
            "com.docker.compose.version": "1.11.2"
        "rpm": {
          "$schema": "",
          "title": "Packages (RPM)",
          "type": "dockerapi",
          "harvestid": "1c2976f2-802c-4138-a6b7-e7a814340fea"

Since Lumogon's output is valid JSON, you can slice and dice it with jq, or pass it along to any other tool you use that can accept JSON input:

docker run --rm  -v /var/run/docker.sock:/var/run/docker.sock puppet/lumogon scan | jq -r  '.containers[] | .container_name + "      " + + "     " +'

/fixtures_debian-jessie_1 debian 8.7 /fixtures_alpine_1 alpine 3.4.0 /fixtures_centos7_1 centos 7.3.1611 /fixtures_fedora_1 fedora 25 /fixtures_centos6_1 centos 6.8 /fixtures_ubuntu-trusty_1 ubuntu 14.04 /fixtures_debian-wheezy_1 debian 7.11 /fixtures_ubuntu-xenial_1 ubuntu 16.04

Sending reports to a backend service

Lumogon provides the ability to submit gathered reports to an optional endpoint of your choosing.

NOTE The Puppet provided reporter backend service and all data has been decommissioned as of May 2018.

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock puppet/lumogon report --endpoint


command generates the same data as
, but sends it to the configured reporting endpoint.

More ways to use Lumogon

The examples directory provides more thorough examples of how to use the data provided by Lumogon to test and build your images and containers.

Lumogon command options

Let's get the usage for the Lumogon client:

docker run --rm  -v /var/run/docker.sock:/var/run/docker.sock puppet/lumogon --help
Lumogon is a tool for inspecting, reporting on, and analyzing your container applications.

Usage: lumogon [command]

Available Commands: help Help about any command report Scan one or more containers and send the collected information to the Lumogon service scan Scan one or more containers and print the collected information version Show the Lumogon version information

Flags: -d, --debug Print debug logging -k, --keep-harvesters Keeps harvester containers instead of automatically deleting

Feel free to explore those command-line options. Of note:

  • The
    flag will preserve temporary containers created on the fly to explore your other containers. You can use
    docker logs 
    to see more of what they found while running.
  • You can specify
    to collect data on all your running containers, or you can target a specific container by passing
  • --debug
    will generate verbose debugging output so you can see how Lumogon explores your containers.

Building the client from source

If you're making changes to Lumogon, or just interested in seeing how it works under the hood, you might want to try building from source. For this you'll need a few more things:

  • Install Go, version 1.8 or later
  • Docker Docker, version 17.05 or later
  • Download the Lumogon source code
  • Build the Docker image

The terminal commands to do this are:

export GOPATH="${HOME}/go"
go get -d -u
cd $GOPATH/src/
make image

This will build the client and package it in the


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.