I am running Dump1090 Mutability in Docker containers. This way I am able to run multiple Dump1090 instances on the same X86 Linux host. It can be useful for testing.
It is also possible to build a Dump1090 container image on one host and run it on other Linux hosts even in the cloud, without the need of repackaging the image. It runs every where!
But my main goal is to make dump1090 scaleable as a real cloud application and being able to serve an extreem amount of users. Running an dynamic amount of dump1090 containers depending on the amount of current users…
Not familiar with Docker containers jet? Containers look like VM’s (virtual machines on VMware, HyperV, Xen, KVM, VirtualBox, etc), but they are much more fast and use less resources. They all share the same kernel. Unlike VM’s on a hypervisor, which all have their own kernel and therefor use much more resources. It is not visualization by a hypervisor, but by isolation of resources. Google and Twitter are using containers for many year and recently the hole world is jumping onto containers. Check http://www.docker.com and https://www.opencontainers.org. And this video: Getting Started with Docker
I have build a X86 container image with Dump1090-Mutability V1.15 and my own heatmap and radarview functionality. The image is available on Docker Hub: https://hub.docker.com/r/tedsluis/dump1090-mutability
If you have already installed Docker on your system (it is available for almost every Linux Distro and for Windows and IOS, check: https://docs.docker.com/engine/installation) you can download, run and use my dump1090 GUI with a single command. But then you get my personal settings and you will see planes in the GUI that are spotted by my antenna
With a little more effort you can build your own Docker container image with our own Dump1090 version. Use my Dockerfile (https://github.com/tedsluis/docker-dump1090) as a starting point and make some changes. Add you own config files and set our own BEAST format source.
This image doesn’t use a RTL SDR receiver with a antenna to gather flight data. Instead it uses an other dump1090 instance that I have running in the Google cloud. It is collecting BEAST format data from that Dump1090 remote source. I use netcat to copy the BEAST data from the remote Dump1090/port 30005 to port 30104 of the Dump1090 in the container. If you use my container you will get my BEAST data. However, I have made it possible to change the BEAST source IP address. SO you can point it to you own Dump1090 receiver. You can find the instructions on Github and DockerHub.
If you are still not convinced that this is cool and easy to do then check my video, where I show all the steps of building and running a dump1090 docker container:
I hope you enough it!