Public | Automated Build

Last pushed: a year ago
Short Description
Metricbeat monitoring for docker hosts
Full Description


This repository contains a collection of "Dockerfile" for their respective automated build in Docker hub,
found at

Note that if your seeing this README directly in docker, chances are you are using one of the images that will
either be in the process of being rewritten. Or replaced;

Issue filling

Any problems / comments / kudos should be filed at github =)

Overhaul in progress

Note that gradually overtime, I would be refactoring these various file to a more structured format

Organized Dockerfile

See their respective README for more details. These Dockerfile, typically represents various iterations,
of all my DevOps docker experiences. Refined for multiple use cases.

Unorganized Dockerfile

Every other folder not in organized Dockerfile, these ranges from awesome, to crap, to not working.

Even I was a Docker noob once, and had to start from somewhere =P


MIT License

This is an obvious choice due to the highly public nature of these Docker repo's and how easy,
or commonly the scripts can be replicated.

For most of the Dockerfiles, I wager that someone out there has something similar.

Hopefully mine is better, Cheers!

Best Regards,
Eugene @

Some general guidelines

  • Follow the standard environment as specified inside (base/README)[]
  • Do not include external files (where practical), echo and write it out in Dockerfile instead.
    • This is because with layers and layers of file add, is un-viewable and un-traceable in Docker hub.
  • Have a sane default for everything (if possible).
    • I want things to be deployable without configuration
    • Exception is for databases, or similar integration
  • For application servers, build using (ubuntu-base)[]
    • For everthing else priotise according to the following : Offical repo, alpine, debian, ubuntu-base
Docker Pull Command
Source Repository