mikenye / docker-readsb

Multi-architecture readsb container with support for RTLSDR, bladeRF and plutoSDR (x86_64, arm32v7, arm64v8)
83 stars 4 forks source link

[HELP] Connect to a FR24 box #5

Closed alexbogus closed 4 years ago

alexbogus commented 4 years ago

Hi,

In order not to have an RTLSDR and a FR24 box, I would like to use the readsb docker container to connect to my FR24 and feed my adsb messages to other platforms or just to see my planes on my own instance of tar1090.

I'm trying to make my docker-compose.yml passing the the next variables, but I have errors whe the docker goes up.

  readsb:
    image: mikenye/readsb:latest
    tty: true
    container_name: readsb
    restart: always
    ports:
      - 8080:80
      - 30005:30005
    networks:
      - adsbnet
    command:
      - --dcfilter
      - --fix
      - --forward-mlat
      - --json-location-accuracy=2
      - --lat=XX.XXX
      - --lon=XX.XXX
      - --mlat
      - --modeac
      - --stats-every=3600
      - --quiet
      - --write-json=/var/run/readsb
      - --net
      - --net-only
      - --net-connector xx.x.xx.xx, 30334, raw

The errors that I haver are:

,/usr/local/bin/readsb: unrecognized option '--net-connector xx.xx.xx.xx, 30334, raw'
,Try `readsb --help' or `readsb --usage' for more information.
,[cmd] /usr/local/bin/readsb exited 64
,[cont-finish.d] executing container finish scripts...
,[cont-finish.d] done.
,[s6-finish] waiting for services.
,[s6-finish] sending all processes the TERM signal.
,[s6-finish] sending all processes the KILL signal and exiting.

This is the architecture that I would like to deploy, just to explore the possibilities and to tinker with.

architecture

Thanks in advance Kind regards

mikenye commented 4 years ago

Hi @alexbogus,

Try this:

  readsb:
    image: mikenye/readsb:latest
    tty: true
    container_name: readsb
    restart: always
    ports:
      - 8080:80
      - 30005:30005
    networks:
      - adsbnet
    command:
      - --dcfilter
      - --fix
      - --forward-mlat
      - --json-location-accuracy=2
      - --lat=XX.XXX
      - --lon=XX.XXX
      - --mlat
      - --modeac
      - --stats-every=3600
      - --quiet
      - --write-json=/var/run/readsb
      - --net
      - --net-only
      - --net-connector=x.x.x.x,30334,raw_in

The --net-connector argument syntax is as follows:

--net-connector=<ip,port,protocol>
Establish connection, can be specified multiple times (e.g. 127.0.0.1,23004,beast_out)
Protocols: beast_out, beast_in, raw_out, raw_in, sbs_out, vrs_out

Let me know if this works.

Kind regards, Mike Nye

alexbogus commented 4 years ago

It's work. Sorry was my mistake, my apologies Thanks for your support, and for the effort of maintain the docker.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
,[s6-init] ensuring user provided files have correct perms...exited 0.
,[fix-attrs.d] applying ownership & permissions fixes...
,[fix-attrs.d] done.
,[cont-init.d] executing container initialization scripts...
,[cont-init.d] done.
,[services.d] starting services
,[services.d] done.
,Fri May  1 09:06:39 2020 UTC  Mictronics v3.8.2 starting up.
,Net-only mode, no SDR device or file open.
,Raw TCP input: Connection established: x.x.x.x port 30334
,

Kind regards Alex

mikenye commented 4 years ago

Hi @alexbogus,

No preblems at all, glad it's working. Thanks for the kind words.

Kind regards, Mike Nye