-
Notifications
You must be signed in to change notification settings - Fork 55
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
STATUS: Exited (0) #141
Comments
I'm using this command: docker run -d -p 8080:8080 -p 8754:8754 --name dump (I have very little experience with docker) |
Same here, in the logs i don't see anything wrong...
|
Eskerrik asko! :) I just followed the tutorial on your blog. |
With a few RPI restarts I see this, so maybe my RTL dongle is dyeing:
|
I am having the same issue albeit on a different system. I’m running this on an odroid N2+. So far I’m trying to figure out if dump1090 can even start and connect to the dongle. From the host OS I ran
and I got a result saying that it connected to the device ok. However it almost seems that the docker container cannot connect… and then just shuts down. Is there a way to run the container in a more verbose / debug mode? |
I did a rpi-update and now, after several reboots, I can make it run for 4-5 minutes. Then the docker dies. |
2023-08-28T09:36:22.946464744Z [dump1090] rtlsdr_demod_write_reg failed with -4 The application can't secure access to the rtl-sdr tuner. I didn't have this issue but apparently sometimes the pi kernel loads default drivers that need to be blacklisted. try some of the links here: https://www.google.co.uk/search?q=blacklist+kernel+rtl-sdr+pi&ie=utf-8&oe=utf-8&aq=t Every now and then I get "rtlsdr_demod_write_reg failed with -7" on two different rtl-sdrs with different apps and a reboot fixes. |
and be sure to follow the instructions here for configuring the pi for rtl-sdr (scroll to the linux section) |
Why I have to deal with this If I'm using a docker enviroment? |
I have just reinstalled a whole RPI OS, docker and docker-compose from scratch and now it is working again. |
I'm trying to run it in docker on a raspberry pi 4. After executing the run command the container successfully starts, but then the STATUS changes to Exited (0).
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: