Update causes device busy about docker-fr24feed-piaware-dump1090 HOT 7 CLOSED

I had the same issue and got it working with setting the /etc/fr24feed.ini like this:

receiver="beast-tcp"
host="127.0.0.1:30005"
fr24key="myfeederID"
bs="yes"
raw="yes"
logmode="1"
procargs="--net --write-json /usr/lib/fr24/public_html/data"

Before i had the receiver set to "dvbt". When i changed it to "beast-tcp" (or avr-tcp) it was suddenly working without the mentioned error.

from docker-fr24feed-piaware-dump1090.

Can you try to disable mlat ?
We already had this issue #14

from docker-fr24feed-piaware-dump1090.

How do I do that? I tried changing the following options to both be "no" without luck.

mlat="yes"
mlat-without-gps="yes"

from docker-fr24feed-piaware-dump1090.

Do you mount the config file or are you using the environment var ?
I recommend you to use the env var, so no need to bind mount any file.
With env you only need to change your credentials (not mlat or anything else).

from docker-fr24feed-piaware-dump1090.

Do you mount the config file or are you using the environment var ?
I recommend you to use the env var, so no need to bind mount any file.
With env you only need to change your credentials (not mlat or anything else).

I tried that before but it seems the export variables for fr24feed.ini were not recognized. So i had to use the mounted file instead :(

The export variables for piaware.conf were working howsoever.

from docker-fr24feed-piaware-dump1090.

Strange I have something like this and it works, maybe you have more options:

    environment:
      - "HTML_SITE_LAT=47.xxxxxx"
      - "HTML_SITE_LON=-1.xxxxxx"
      - "HTML_SITE_NAME=HOME"
      - "FR24FEED_FR24KEY=xxxxxx"
      - "PIAWARE_FEEDER_DASH_ID=xxxxxxx"

from docker-fr24feed-piaware-dump1090.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-fr24feed-piaware-dump1090.