search

sdr-enthusiasts / docker-adsb-ultrafeeder

ADSB-Ultrafeeder is an all-in-one ADSB container with readsb, tar1090, graphs1090, autogain, multi-feeder, and mlat-hub built in
GNU General Public License v3.0
180 stars 32 forks source link

Ultrafeeder is not creating /run/readsb on fresh install #120

Closed CurtisDufour closed 2 months ago

CurtisDufour commented 2 months ago

I have a fresh install of Ultrafeeder that does not seem to be starting readsb. the only configurations I have performed are adding my .env information. if I run the command docker compose up it gives me the following data:

[+] Running 1/0 ✔ Container ultrafeeder Running 0.0s Attaching to ultrafeeder ultrafeeder | [collectd] Waiting for readsb to start... ultrafeeder | [2024-07-29 17:56:59.681][tar1090] runtime directory (first argument: /run/readsb) is not a directory, fatal error! ultrafeeder | [2024-07-29 17:57:05.714][tar1090] runtime directory (first argument: /run/readsb) is not a directory, fatal error! ultrafeeder | [collectd] Waiting for readsb to start... ultrafeeder | [2024-07-29 17:57:11.756][tar1090] runtime directory (first argument: /run/readsb) is not a directory, fatal error! ultrafeeder | [collectd] Waiting for readsb to start... ultrafeeder | [2024-07-29 17:57:17.799][tar1090] runtime directory (first argument: /run/readsb) is not a directory, fatal error!

If I run docker exec -it ultrafeeder /usr/local/bin/viewadsb, it says 'Beast TCP input: Connection to 127.0.0.1 port 30005 failed: 111 (Connection refused)'.

I have not had any of these errors ever happen before. I have tried to remove the image for ultrafeeder, I have tried re-downloading the docker compose file for ultrafeeder, nothing appears to be helping. Any idea what is going wrong here?

CurtisDufour commented 2 months ago

Sorry... I guess I needed to just leave it running and come back two hours later!