You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running in an unprivileged Docker container, everything functionally works fine as long as the proper USB device is passed in, but piaware-status reports:
root@98cec28c1d21:/# piaware-status
PiAware master process (piaware) is running with pid 52.
PiAware ADS-B client (faup1090) is running with pid 90.
PiAware mlat client (fa-mlat-client) is running with pid 92.
Local ADS-B receiver (dump1090-fa) is running with pid 69.
unknown process (pid unknown) is listening for connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is NOT connected to FlightAware.
dump1090 is producing data on localhost:30005.
Your feeder ID is [UUID] (configured at /etc/piaware.conf:9)
This is because socket to PID mappings aren't available:
piaware-status should probably check for this situation; e.g. ":1200" and program "-" should report something like "piaware is probably connected to FlightAware, but cannot be certain due to environment restrictions." instead of "piaware is NOT connected to FlightAware."
The text was updated successfully, but these errors were encountered:
When running in an unprivileged Docker container, everything functionally works fine as long as the proper USB device is passed in, but
piaware-status
reports:This is because socket to PID mappings aren't available:
piaware-status
should probably check for this situation; e.g. ":1200" and program "-" should report something like "piaware is probably connected to FlightAware, but cannot be certain due to environment restrictions." instead of "piaware is NOT connected to FlightAware."The text was updated successfully, but these errors were encountered: