FoxxMD

Thanks @Ding Dong Del I have added the extra parameters advice to the OP. If more users comment saying that works for them then I will update the template to add it as a default -- @DarkstarLux @waveworm @Fpsware @mikeydk And thanks everyone else for feedback on DB connections. I've personally only used it with postgres so wasn't aware there was an issue with mysql. Glad sqlite is working! P.S. I am not the maintainer of this docker (just the unraid template! 😬) so I can't do anything about PUID/PGID and TZ as variables but I will open an issue on the author's repo asking about it!

@PSYCHOPATHiO ive mentioned that issue in the support thread! In the docker settings set mlat and mlat w/o gps to no.

Application Name: statping Application Site: https://demo.statping.com Github Repo: https://github.com/hunterlong/statping Docker Hub: https://hub.docker.com/r/statping/statping Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview Statping is an easy to use Status Page for your websites and applications. Statping will automatically fetch the application and render a beautiful status page with tons of features for you to build an even better status page. This Status Page generator allows you to use MySQL, Postgres, or SQLite on multiple operating systems. There are also statping client apps available for iphone/android. Requirements A database (mysql/postgres/sqlite) connection Some users report mysql does not currently work Usage On startup save your database connection through the Web UI. You're done! Refer to the project site for more info on setting up plugins, etc. Troubleshooting user doesn't have permission to write to this directory In the Advanced View of the app edit page add the following the extra parameters field --user 99:100 Error 1298: Unknown or incorrect time zone: 'UTC' Ensure the timezone is properly set and passed to the container as a variable using the key TZ

@jandro4321 The dockerfile does not expose port 8080 (which is where the internal webserver serves from) and I'm also not sure if any extra is required to start the internal webserver, other than starting dump1090. This is a question @ShoGinn would be able to answer! However you can also use shoginn-vrs (in Community Apps) to get a much more fully featured aircraft tracking app and use this app as the data source for it.

Application Name: shoginn-vrs Application Site: http://virtualradarserver.co.uk Github Repo: https://github.com/ShoGinn/virtualradarserver-docker Docker Hub: https://hub.docker.com/r/shoginn/vrs @ShoGinn <3 Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview Virtual Radar Server is an open-source .NET application used to overlay and track the real time position of aircraft on a map within a modern browser. VRS can receive aircraft data from a multitude of sources including ADS-B streams. Requirements A configuration directory (default mapped to /mnt/user/appdata/vrs) A port exposed for the web ui (default mapped to 8117) Optionally, if you want to see anything, you will need to configure at least one Receiver (data source). I highly recommend a cheap RTL-SDR usb device and shoginn-dump1090, available in Community Apps Usage (Setup) The Admin Interface can be accessed at http://IP:PORT/VirtualRadar/WebAdmin/Index.html Adding a Data Source (Receiver) Access the Admin Interface Navigate to Options => Receiver Locations Add a new Location with the Lat/Long of your data source Navigate to Options => Receivers Add a new Receiver and specify Location from the dropdown as the one added from above Use these settings if you are using shoginn-dump1090: Format: AVR or Beast Raw Feed | Address: [IP of dump1090] | Port: [Port of dump1090] Check "Send keep-alive packets" Make sure to hit Save at the bottom of the page! Your data source is now setup and should be feeding VRS. You can verify this by going to Connector Activity Log (located on the Admin Interface). Saving Default Client Settings (Map Location, etc.) Navigate to the Web UI for shoginn-vrs In the top-left corner navigate Menu => Options To set default Map Location On the General tab click "Set current location", then drag the marker to the desired center position on the map Set any other default settings in the Options window at this time, then close it In a new window navigate to http://IP:PORT/VirtualRadar/settings.html Click Export Settings Copy all of the text in the input box that appears In the Admin Interface navigate to Options => Initial Settings Paste the contents of the input box into the input box for Exported settings Save your changes at the bottom of the page Using VRS with a reverse proxy (nginx) Refer to this comment for how to setup VRS behind a reverse proxy.

Application Name: shoginn-flightaware Application Site: https://uk.flightaware.com/adsb/flightfeeder/ Github Repo: https://github.com/ShoGinn/flightaware Docker Hub: https://hub.docker.com/r/shoginn/flightaware @ShoGinn <3 Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview FlightAware is a digital aviation company that operates a flight tracking and data platform. This docker contains the binary for FlightAware's FlightFeeder application, which consumes an ADSB feed and uploads the parsed data to FA. Usage To properly use this docker you must have: A sharing key received by registering an account on FA and then claiming a new receiver. An ADSB feed for the application to consume. If you have a radio device, like an RTL-SDR, you can use shoginn-dump1090 to create this feed. (Additional instructions on how to passthrough your RTL-SDR usb device are in the linked thread

Application Name: shoginn-flightradar24 Application Site: https://www.flightradar24.com/share-your-data Github Repo: https://github.com/ShoGinn/flightradar24 Docker Hub: https://hub.docker.com/r/shoginn/flightradar24 @ShoGinn <3 Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview FlightRadar24 is a Swedish internet-based service that shows real-time commercial aircraft flight information on a map. This docker contains FR24's binary for consuming an ADSB feed and uploading the parsed data to FR24. Usage To properly use this docker you must have: A sharing key received by registering an account on FR24 and "activating" a new receiver. An ADSB feed for the application to consume. If you have a radio device, like an RTL-SDR, you can use shoginn-dump1090 to create this feed. Note: There is a known bug in the current binary builds of fr24's application. If your container crashes during startup try setting mlat and mlat w/o gps to no.

@PSYCHOPATHiO Gone are the days where only the container your rtl-sdr device is attached to can use it -- now that you can expose the port it is feeding to anything can consume it! I didn't have time to get these published today but I have templates for flightradar24 and flightaware that I will hopefully get published tomorrow. You can consume the adsb data from dump1090 using those dockers. @ShoGinn has additional dockers I haven't had a chance to look at yet that can also consume this data. Perhaps a self-hosted flight tracker web ui as well? Stay tuned! I'll have more apps within this ecosystem up shortly (and will edit the OP when they are)

Application Name: shoginn-dump1090 Application Site: https://github.com/flightaware/dump1090 Github Repo: https://github.com/ShoGinn/dump1090 Docker Hub: https://hub.docker.com/r/shoginn/dump1090 @ShoGinn❤️ Template Repo: https://github.com/FoxxMD/unraid-docker-templates Overview dump1090 is a program that outputs ADSB data by decoding it from a software-accessible radio device. This data can be used to identify and track aircraft. This application works well with these other community apps: Usage dump1090 is typically used in conjunction with one or more other applications that consume the data it outputs. This application template provides default port mapping for the two types of data feeds, raw and BEAST, which these other applications will consumes. You must map a compatible host device into this container in order for dump1090 to work properly (instructions linked). In most cases this is an RTL-SDR usb device.

@PSYCHOPATHiO I'd wager the change was an update to an intermediate layer in the build. I'm a little behind my expected time for working on getting @ShoGinn's repos written up as templates 😅 but I finally have some free time! Should probably have these up on CA in the next weekish. Hopefully their more up to date/modular approach will help solve some of the issues people have been having this thread.

@klausagnoletti I'm sorry but I can't help you with your specific issues, I don't run an ELK stack and don't have experience with logstash/kibana. You probably aren't finding what you're looking for because: 1. ELK is an orchestration of services. Unraid lets you run individual dockers (docker-compose is not available) so an ELK stack can't be easily packaged up and deployed as "one docker" for unraid. 2. Unraid's apps are basically just templates/configuration presets for docker images from dockerhub. There is nothing special about docker images run on unraid other than the app creator can provide some convenience to other unraid users. These templates don't provide any extra functionality not already found in the docker image from dockerhub. Having said that you can easily run any docker image from dockerhub, as you have discovered. I suspect your issue is an unfamiliarity with the ELK stack, not docker -- as docker is usually pretty transparent. If you can setup an ELK stack in a regular environment you shouldn't have much trouble doing it with docker containers. Some tips that might help you though with template configuration for docker containers in unraid: variable - an environmental variable provided to the docker container. Elasticsearch requires the variable discovery.type to be provided so you would created variable named discovery.type and put its value to single-node directory/folder mapping -- provides mapping from a local directory (in your array) to a directory of your choosing in the docker container. If the ELK stack requires shared files between the services you could setup a folder /mnt/user/appdata/elk that is mapped to all three dockers. port - a local port (on the host machine) mapped to a port in the docker container. If need to point docker container A to docker container B you would give it the host IP + local (mapped) port of container B. EX elasticsearch exposes port 9200. port mapping could be 9200 (docker) -> 8200 (local). If kibana needed to access elasticsearch you would map a variable elastic_endpoint to 192.168.0.1:8200 (or whatever your host IP is)

Unraid has been the perfect balance of a turnkey JBOD server solution and configurability. I love that I didn't have to do anything have a dashboard, network sharing administration, and docker/vm usage -- but at the same time any time something in unraid isn't totally cutting it I can easily dive into the terminal or create a user script. Oh and of course CA has been absolutely intrumental in turning my hardware into something useful.

@yayitazale @craig_read Here are the contents of my various files. I think maybe the repo author hasn't updated the samples in awhile. Maybe these will help you: fr24feed.ini receiver="dvbt" fr24key="your_key_here" bs="yes" raw="yes" logmode="1" mpx="no" mlat="yes" mlat-without-gps="yes" procargs="--net --write-json /usr/lib/fr24/public_html/data" the last argument, procargs, is what actually feeds data into the map. its important that it exists piaware.conf # This file configures piaware and related software. # You can edit it directly or use piaware-config from the command line # to view and change settings. # # If /boot/piaware-config.txt also exists, then settings present in # that file will override settings in this file. flightaware-user FoxxMD flightaware-password myPass feeder-id myId allow-mlat yes mlat-results yes My config.js is essentially the same and upinair.json is optional (and specific to your location)

Yes, you need an antenna and a USB SDR, like this, in order to run this software.

@khile Check the instructions. You need to go to the FR24 website, register an account, and apply for a key.

@yayitazale from the logs you posted you can see piaware is not staying up 2019-07-07 20:27:35,450 INFO exited: piaware (exit status 4; not expected) Taking a look at the piaware source we see that exit code 4 is used when login fails. I'm guessing the container becomes unresponsive because supervisord is constantly trying to restart the process.

@yayitazale The first block you quoted about config is specific to setting up shinysdr. In that post you only need to follow through Step 5 in order to passthrough the device. I have not had the time to create templates for @ShoGinn's dockers yet. Can you post a more complete container log? It's hard to tell what is going on from the excerpt you gave. My guess is that you are missing some configuration or have not correctly passed through the device to the container.

@vw-kombi elasticsearch is just a backend service. It does not provide a UI but rather is used by other applications to query for data. When you are visiting the HTTP port you are making a simple API request and ES sends a response in the same format it would send all other data in -- so the text you got back in your first post is basically a sample of how all data returned from ES will look. There are a few web-based frontends for querying and viewing this data: https://www.elastic.co/guide/en/sense/current/introduction.html https://github.com/appbaseio/dejavu But from your description of what you want I have a feeling that's not what you are looking for. I did find this tutorial for a simple full-text search https://github.com/triestpa/Guttenberg-Search but you would have to write a new Dockerfile for it and publish it to DockerHub to make it useable on unraid.

@vw-kombi no that's it! It's up and working correctly.

Glad you got it figured out! I'm not sure about that downloader, I'm pretty new to the booru scene myself. I'm using this one as a private meme library without much other functionality ¯\_(ツ)_/¯

I don't know about automatically running it but you could put a script in CA User Scripts that makes it a one-click operation after the container is running. I haven't test this but it should be close to working: #!/bin/bash # Return name of docker container with elasticsearch in it -- assuming only one container for elasticsearch is present con="$(docker ps --format "{{.Names}}" | grep -i elasticsearch)" # execute command inside container docker exec -i "$con" /usr/share/elasticsearch/bin/elasticsearch-plugin install --batch ingest-attachment

Glad I could get you hooked! Fortunately its a relatively cheap hobby at least until you want to start transmitting... 😬 I'm using the same configuration right now -- one receiver/antennae for dump1090-piaware-etc. and one beefier receiver/antennae for use with my ShinySDR container for messing around. On that note ethough, @PSYCHOPATHiO let me know if you run into any issues passing through both devices, I'm struggling with my second device. P.S. @ShoGinn I'm still planning on writing templates for your dockers! I have been in the process of moving these last two weeks so haven't had much spare time..

I'd be happy to write these for you and add them to my repo if you'd like!

@darvvyn the docker maintainer has just updated the image with a plugin that supports decoding digital voice. I won't be able to test that this works until later next week but if you can check it out and report back!

@ShoGinn thanks for the insight! I'd much rather be running dump1090/fa/fr as separate dockers and yours look very clean. Please let me know when you get to multi-arch!