Build new docker image from repo ?

[n9yty]

I was interested in trying the new auto-token feature I saw in a recent commit. I am running protect on a cloud key gen2 plus and I can not get the manual device add to work/appear so I thought maybe the auto token generation would help.

I tried to build a new docker image from the repo using:

$ docker build https://github.com/keshavdv/unifi-cam-proxy.git#main

It started out well but eventually dies.

That could be the other project's problem, I'm not familiar with this process unfortunately.

I checked out the repo locally to modify the Dockerfile and changed the base to be 'python:3.11-alpine3.16' (due to warning about old pip version), changed ffmpeg to 5.0.1-r1 due to an error about that version, then added 'rust cargo' to the second 'RUN apk add' line. The image built, but it is substantially heavier and untested. I went back to the original, just adding rust and cargo and it built, but I get this in the log:

Traceback (most recent call last):
  File "/usr/local/bin/unifi-cam-proxy", line 5, in <module>
    from unifi.main import main
  File "/usr/local/lib/python3.8/site-packages/unifi/main.py", line 6, in <module>
    from pyunifiprotect import ProtectApiClient
  File "/usr/local/lib/python3.8/site-packages/pyunifiprotect/__init__.py", line 2, in <module>
    from pyunifiprotect.api import ProtectApiClient
  File "/usr/local/lib/python3.8/site-packages/pyunifiprotect/api.py", line 21, in <module>
    from pyunifiprotect.data import (
  File "/usr/local/lib/python3.8/site-packages/pyunifiprotect/data/__init__.py", line 1, in <module>
    from pyunifiprotect.data.base import (
  File "/usr/local/lib/python3.8/site-packages/pyunifiprotect/data/base.py", line 26, in <module>
    from pyunifiprotect.data.types import (
  File "/usr/local/lib/python3.8/site-packages/pyunifiprotect/data/types.py", line 32, in <module>
    class FixSizeOrderedDict(dict[KT, VT]):
TypeError: 'type' object is not subscriptable

Any advice for building?

Here was the original failure error:

Collecting orjson
  Downloading orjson-3.8.1.tar.gz (860 kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'error'
  ERROR: Command errored out with exit status 1:
   command: /usr/local/bin/python /usr/local/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-raibhd19/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- 'maturin>=0.13,<0.14'
       cwd: None
  Complete output (55 lines):
  Collecting maturin<0.14,>=0.13
    Downloading maturin-0.13.7.tar.gz (154 kB)
    Installing build dependencies: started
    Installing build dependencies: finished with status 'done'
    Getting requirements to build wheel: started
    Getting requirements to build wheel: finished with status 'done'
      Preparing wheel metadata: started
      Preparing wheel metadata: finished with status 'done'
  Collecting tomli>=1.1.0; python_version < "3.11"
    Using cached tomli-2.0.1-py3-none-any.whl (12 kB)
  Building wheels for collected packages: maturin
    Building wheel for maturin (PEP 517): started
    Building wheel for maturin (PEP 517): finished with status 'error'
    ERROR: Command errored out with exit status 1:
     command: /usr/local/bin/python /usr/local/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmp69pte_z0
         cwd: /tmp/pip-install-96adxyyi/maturin
    Complete output (32 lines):
    running bdist_wheel
    running build
    running build_py
    creating build
    creating build/lib.linux-x86_64-cpython-38
    creating build/lib.linux-x86_64-cpython-38/maturin
    copying maturin/__init__.py -> build/lib.linux-x86_64-cpython-38/maturin
    copying maturin/import_hook.py -> build/lib.linux-x86_64-cpython-38/maturin
    copying maturin/__main__.py -> build/lib.linux-x86_64-cpython-38/maturin
    running egg_info
    creating maturin.egg-info
    writing maturin.egg-info/PKG-INFO
    writing dependency_links to maturin.egg-info/dependency_links.txt
    writing requirements to maturin.egg-info/requires.txt
    writing top-level names to maturin.egg-info/top_level.txt
    writing manifest file 'maturin.egg-info/SOURCES.txt'
    reading manifest file 'maturin.egg-info/SOURCES.txt'
    reading manifest template 'MANIFEST.in'
    writing manifest file 'maturin.egg-info/SOURCES.txt'
    running build_ext
    running build_rust
    error: can't find Rust compiler
  
    If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.
  
    To update pip, run:
  
        pip install --upgrade pip
  
    and then retry package installation.
  
    If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
    ----------------------------------------
    ERROR: Failed building wheel for maturin
  Failed to build maturin
  ERROR: Could not build wheels for maturin which use PEP 517 and cannot be installed directly
  WARNING: You are using pip version 20.1.1; however, version 22.3.1 is available.
  You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
  ----------------------------------------
ERROR: Command errored out with exit status 1: /usr/local/bin/python /usr/local/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-raibhd19/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://pypi.org/simple -- 'maturin>=0.13,<0.14' Check the logs for full command output.
WARNING: You are using pip version 20.1.1; however, version 22.3.1 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.

[n9yty]

Okay, it seems the new bits for the auto token require python 3.9...

Current Dockerfile:

FROM python:3.11-alpine
WORKDIR /app

RUN python -m pip install --upgrade pip
RUN apk add --update gcc libc-dev linux-headers libusb-dev
RUN apk add --update ffmpeg=5.0.1-r1 netcat-openbsd git rust cargo

COPY . .
RUN pip install .

COPY ./docker/entrypoint.sh /

ENTRYPOINT ["/entrypoint.sh"]
CMD ["unifi-cam-proxy"]

My Reolink camera came online and automatically added itself to Protect, so that is a win. However, the video stream doesn't work, I get the image with three flashing dots in the lower left.

But progress... :)

[n9yty]

The video may be an artifact of having to update the ffmpeg version... ??

docker-compose.yml portion:

command: unifi-cam-proxy -H <nvripredacted> -i <camipredacted> --cert /client.pem --nvr-username <redacted> --nvr-password <redacted> reolink -u <redacted> -p <redacted> -s "main" --ffmpeg-args='-c:v copy -vbsf "h264_metadata=tick_rate=60000/1001" -ar 32000 -ac 1 -codec:a aac -b:a 32k'

Log:

ffmpeg version 5.0.1 Copyright (c) 2000-2022 the FFmpeg developers
built with gcc 11.2.1 (Alpine 11.2.1_git20220219) 20220219
   configuration: --prefix=/usr --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libpulse --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-lto --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-librist --enable-libsrt --enable-libssh --enable-libvidstab --disable-stripping --disable-static --disable-librtmp --enable-libaom --enable-libopus --enable-libsoxr --enable-libwebp --enable-vaapi --enable-vdpau --enable-vulkan --enable-libdrm --disable-debug
   libavutil      57. 17.100 / 57. 17.100
   libavcodec     59. 18.100 / 59. 18.100
   libavformat    59. 16.100 / 59. 16.100
   libavdevice    59.  4.100 / 59.  4.100
   libavfilter     8. 24.100 /  8. 24.100
   libswscale      6.  4.100 /  6.  4.100
   libswresample   4.  3.100 /  4.  3.100
   libpostproc    56.  3.100 / 56.  3.100
2022-11-15 19:16:14 f83b20f24886 Reolink[1] WARNING Previous ffmpeg process for video2 died.
2022-11-15 19:16:14 f83b20f24886 Reolink[1] INFO Spawning ffmpeg for video2 (tCZckbl9Wm2sem9i): ffmpeg -nostdin -loglevel error -y -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1 -timeout 15000000 -rtsp_transport tcp -i "rtsp://admin:<pwredacted>@<ipredacted>:554//h264Preview_01_main" -ar 32000 -ac 1 -codec:a aac -b:a 32k -c:v copy -vbsf "h264_metadata=tick_rate=14" -metadata streamName=tCZckbl9Wm2sem9i -f flv - | /usr/local/bin/python -m unifi.clock_sync --write-timestamps | nc <ipredacted> 7550

[n9yty]

Further, looking at the source, I don't see where the parameter "--ffmpeg-args" is even being parsed. Perhaps the documentation is out of date, much like the add camera URL to get a token has changed and is not documented but rather I found that info in another discussion post. (UPDATE: I do see --ffmpeg-args in the base camera class, but it doesn't seem to be used for the Reolink camera? At least it isn't using the string I provide based on the documentation. It seems the reolink class overrides it and doesn't allow a user customization.)

[bigjools]

Just tried this all out for the first time. My ffmpeg process is constantly dying and being restarted. I get thumbnails in the Protect app but no live video or playback.

unifi-cam-proxy-unifi-cam-proxy-1  | [rtsp @ 0x7f7eee0ca2c0] method DESCRIBE failed: 404 Stream Not Found
unifi-cam-proxy-unifi-cam-proxy-1  | rtsp://admin:<pw-redacted>@<ip-redacted>:554//h264Preview_01_main: Server returned 404 Not Found

(Running from the Docker image)

I'd like to dive in and help (I'm a Python coder by trade) but not sure where to start.