Comment on page
If you wish to feed ADSBHub, follow the steps below.
The docker image
ghcr.io/sdr-enthusiasts/docker-adsbhubcontains the required feeder software and all required prerequisites and libraries. This needs to run in conjunction with
ultrafeeder(or another Beast provider).
First-time users should obtain a ADSBHub Station dynamic IP key. Follow the directions for steps 1 and 2 at ADSBHub how to feed, ensuring your station is set up as a client and the data protocol set as "SBS".
Existing users should sign in to their ADSBHub account, go to their "Settings" page, click on their station (in the bar at the top of the settings table) and retrieve their station key.
In your station preferences, you should set the following:
- Feeder type:
- Data Protocol:
- Station mode:
Inside your application directory (
/opt/adsb), edit the
.envfile using your favourite text editor. Beginners may find the editor
nanoeasy to use:
This file holds all of the commonly used variables (such as our latitude, longitude and altitude). We're going to add our ADSBHub Station Key to this file. Add the following line to the file:
YOURSTATIONKEYwith the station key you retrieved earlier.
- The single quotes (
') are important, as the station key from ADSBHub contains special characters that would confuse
docker composeif the single quotes were missing.
docker-compose.ymlfile that was created when deploying
Append the following lines to the end of the file (inside the
To explain what's going on in this addition:
- We're creating a container called
adsbhub, from the image
- We're passing several environment variables to the container:
SBSHOST=ultrafeederto inform the feeder to get its ADSB data from the container
TZwill use the
FEEDER_TZvariable from your
CLIENTKEYwill use the
ADSBHUB_STATION_KEYvariable from your
Once the file has been updated, issue the command
docker compose up -din the application directory to apply the changes and bring up the
adsbhubcontainer. You should see the following output:
ultrafeeder is up-to-date
piaware is up-to-date
fr24 is up-to-date
pfclient is up-to-date
We can view the logs for the environment with the command
docker logs adsbhub, or continually "tail" them with
docker logs -f adsbhub. The logs will be fairly unexciting and look like this:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] 01-adsbhubclient: applying...
[fix-attrs.d] 01-adsbhubclient: exited 0.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-adsbhubclient: executing...
[cont-init.d] 01-adsbhubclient: exited 0.
[services.d] starting services