-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker-piaware not recieving messages from readsb-protobuf #67
Comments
Hi Henk, Are you using docker-compose? If so, you should specify the container name instead of a loopback address for the Without docker, if you were running these binaries on the host you’d be absolutely correct. However, when running inside a container, the loopback address points to the local container and not the underlying host. If you called your readsb container “ If you aren’t using docker-compose, you have a couple of options:
I hope this helps! Kind regards, |
Hello Mike, I was not using Docker-Compose to be honest have not used Docker-Compose before. I set it up now using Docker-Compose folowing your Gitbook and it all works. Thank you very much |
Hi @hjboven, I'm glad you got it working mate! |
Hi Mike
Just discovered your images yesterday and the seem to build an extremly nice environment to replace my standalone Piaware feeder. I'm using a Raspberry Pi 3b+ with Ubuntu Server 20.04 for Rasberry on it. Works like a charm.
So far I've got readsb-protobuf installed and it seem to work fine.
"docker exec -it readsb viewadsb" shows me a nice Table with plenty of recieved messages. Also the graphical output on port 8080 works just fine.
But when I start docker-piaware it reports
"0 msgs recv'd from dump1090 (0 in last 5m); 0 msgs sent to FlightAware"
Somehow I do not seem to get the connection working between the Containers.
I'm using BEASTHOST | 127.0.0.1 but when i change it to the ip address of the Host the result stays the same.
Do you happen to know what I am missing from your manual in Github??
regards,
Henk
The text was updated successfully, but these errors were encountered: