sonarr-sma docker -- having issues trying to get ffmpeg to work with nvidia. about sickbeard_mp4_automator

[wdckwrth]

Glad to hear that it is working. You can try updating your config.

[Converter]
ffmpeg = ffmpeg
ffprobe = ffprobe
threads = 0
hwaccels = cuda, nvenc, cuvid, vaapi, dxva2, qsv, d3dllva
hwaccel-decoders = h264_cuda, hevc_cuvid, h264_cuvid, mjpeg_cuvid, mpeg1_cuvid, mpeg2_cuvid, mpeg4_cuvid, vc1_cuvid, hevc_qsv, h264_qsv, hevc_vaapi, h264_vaapi
hwdevices = cuda:0
hwaccel-output-format = cuda:cuvid

I haven't found a reason to "need" the newer version.

[mdhiggins]

Unfortunately with linuxserver sonarr migrating to alpine I'm not aware of any FFMPEG builds or binaries that are alpine compatible

[BastionNtB]

I gotcha. Does that make sonarr/radarr-sma docker's obsolete then? Is there an alternative build for sonarr that uses the old ubuntu? Or is it just sourcing an ffmpeg with nvenc for alpine?

Edit: https://github.com/jrottenberg/ffmpeg shows an alpine build for 4.3, but not sure if it supports nvenc or not

I take it the custom build workflows weren't designed for alpine? That's why I was getting errors?

[BastionNtB]

I'm trying to rebuild it using the custom workflow using an older version of sonarr, since I still have a db backup from 3.0. But it doesn't seem to go from alpine to ubuntu. Seems to still use alpine as the OS. I really am not 100% on how this all works, so let me know if I'm doing something wrong.

services:
  sonarr:
    container_name: sonarr
    hostname: sonarr
    #image: mdhiggins/sonarr-sma:latest
    build:
      context: https://github.com/mdhiggins/sonarr-sma.git#build
      args:
        - ffmpeg_tag=4.3-nvidia
        - sonarr_tag=3.0.10.1567-ls218
    runtime: nvidia # Expose NVIDIA GPUs

edit: Ok so, I didn't actually delete the old image, so that's my bad.

However, it can't make the build when I'm using the sonarr_tag and setting a version number like I show above.

I've tried 3, 3.0, amd64-3, etc. Essentially at this point, i'm just trying to go back to v3 of sonarr so that sma will work with it.

[mdhiggins]

The change to alpine for Sonarr at least took place like a week ago

[BastionNtB]

So the last update for sonarr v3 was 2 weeks ago, it should be on ubuntu. However, I'm having trouble with getting the build context/args to build sonarr based on a specific version.

failed to deploy a stack: failed to solve: ghcr.io/linuxserver/sonarr:amd64-3: ghcr.io/linuxserver/sonarr:amd64-3: not found
failed to deploy a stack: failed to solve: ghcr.io/linuxserver/sonarr:3: ghcr.io/linuxserver/sonarr:3: not found
failed to deploy a stack: failed to solve: ghcr.io/linuxserver/sonarr:3.0.10.1567: ghcr.io/linuxserver/sonarr:3.0.10.1567: not found
failed to deploy a stack: failed to solve: ghcr.io/linuxserver/sonarr:3.0.10.1567-ls218: ghcr.io/linuxserver/sonarr:3.0.10.1567-ls218: not found

No matter what version I put in there, if it seems if it's not 'latest' or 'develop' it just doesn't exist... Is there no way to go back to sonarr v3 in docker?

[BastionNtB]

Ok, so I found a 3.0 build that /should/ work but I'm not sure if this is an error from your workflow using the custom build context or if it's something else. Here is the compose

services:
  sonarr:
    container_name: sonarr
    hostname: sonarr
    #image: mdhiggins/sonarr-sma:latest
    build:
      context: https://github.com/mdhiggins/sonarr-sma.git#build
      args:
        - sonarr_tag=3.0.10
    runtime: nvidia # Expose NVIDIA GPUs
    restart: always
    networks:
      - reverseproxy-network
    ports:
      - 8989:8989
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      #- SMA_HWACCEL=true
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
      - NVIDIA_VISIBLE_DEVICES=all
      - UMASK=0002

Here is the error I get when I attempt to pull the image.

"failed to deploy a stack: failed to solve: process "/bin/sh -c if [ -f /usr/bin/apt ]; then apt-get update && apt-get install -y git wget python3 python3-pip python3-venv ${extra_packages} && apt-get purge --auto-remove -y && apt-get clean && rm -rf /tmp/* /var/lib/apt/lists/* /var/tmp/; elif [ -f /sbin/apk ]; then apk update && apk add --no-cache git wget python3 py3-pip py3-virtualenv ${extra_packages} && apk del --purge && rm -rf /root/.cache /tmp/; fi && mkdir ${SMA_PATH} && git config --global --add safe.directory ${SMA_PATH} && git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git ${SMA_PATH} && python3 -m virtualenv ${SMA_PATH}/venv && ${SMA_PATH}/venv/bin/pip install -r ${SMA_PATH}/setup/requirements.txt && chgrp users /usr/local/bin/ffmpeg && chgrp users /usr/local/bin/ffprobe && chmod g+x /usr/local/bin/ffmpeg && chmod g+x /usr/local/bin/ffprobe" did not complete successfully: exit code: 1
"

According to the build digest https://hub.docker.com/layers/linuxserver/sonarr/3.0.10/images/sha256-27723f74f9d31068cdf1fa495d9ed255b0f15d5f41e659520468be22ec6382b0?context=explore

The image is using ubuntu/debian so in theory, this should still work. but I think the build context workflow is attempting to use apk instead of apt?

[mdhiggins]

Notice that command is wrapped in an 'if/else' statement which looks for apt and if not present falls back to apk, its meant to be used in either environment (this same logic is used in lots of the linuxserver back scripts and other scripts in the SMA docker containers; this helps prevent me from having to rewrite the containers every time they switch between)

There should be some more information in the logs about why that command failed, the exit code 1 just means one of those many commands didn't work. If you can find that info I can dig in a little further as to what part of the command failed

[BastionNtB]

Here are the logs

sonarr-sma-build-logs.txt

This is the part of it that crashes

#9 33.47 /usr/bin/python3: No module named virtualenv
#9 ERROR: process "/bin/sh -c if [ -f /usr/bin/apt ]; then     apt-get update &&     apt-get install -y       git       wget       python3       python3-pip       python3-venv       ${extra_packages} &&     apt-get purge --auto-remove -y &&     apt-get clean &&     rm -rf       /tmp/*       /var/lib/apt/lists/*       /var/tmp/*;   elif [ -f /sbin/apk ]; then     apk update &&     apk add --no-cache       git       wget       python3       py3-pip       py3-virtualenv       ${extra_packages} &&     apk del --purge &&     rm -rf       /root/.cache       /tmp/*;   fi &&   mkdir ${SMA_PATH} &&   git config --global --add safe.directory ${SMA_PATH} &&   git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git ${SMA_PATH} &&   python3 -m virtualenv ${SMA_PATH}/venv &&   ${SMA_PATH}/venv/bin/pip install -r ${SMA_PATH}/setup/requirements.txt &&   chgrp users /usr/local/bin/ffmpeg &&   chgrp users /usr/local/bin/ffprobe &&   chmod g+x /usr/local/bin/ffmpeg &&   chmod g+x /usr/local/bin/ffprobe" did not complete successfully: exit code: 1
------
 > [sonarr stage-1 4/6] RUN   if [ -f /usr/bin/apt ]; then     apt-get update &&     apt-get install -y       git       wget       python3       python3-pip       python3-venv       ${extra_packages} &&     apt-get purge --auto-remove -y &&     apt-get clean &&     rm -rf       /tmp/*       /var/lib/apt/lists/*       /var/tmp/*;   elif [ -f /sbin/apk ]; then     apk update &&     apk add --no-cache       git       wget       python3       py3-pip       py3-virtualenv       ${extra_packages} &&     apk del --purge &&     rm -rf       /root/.cache       /tmp/*;   fi &&   mkdir /usr/local/sma &&   git config --global --add safe.directory /usr/local/sma &&   git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git /usr/local/sma &&   python3 -m virtualenv /usr/local/sma/venv &&   /usr/local/sma/venv/bin/pip install -r /usr/local/sma/setup/requirements.txt &&   chgrp users /usr/local/bin/ffmpeg &&   chgrp users /usr/local/bin/ffprobe &&   chmod g+x /usr/local/bin/ffmpeg &&   chmod g+x /usr/local/bin/ffprobe:
29.11 Setting up libalgorithm-diff-xs-perl (0.04-6build3) ...
29.11 Setting up libalgorithm-merge-perl (0.08-3) ...
29.11 Setting up libpython3-dev:amd64 (3.10.6-1~22.04) ...
29.11 Setting up python3-dev (3.10.6-1~22.04) ...
29.11 Processing triggers for libc-bin (2.35-0ubuntu3.1) ...


30.91 0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
30.95 Cloning into '/usr/local/sma'...
33.47 /usr/bin/python3: No module named virtualenv
------
failed to solve: process "/bin/sh -c if [ -f /usr/bin/apt ]; then     apt-get update &&     apt-get install -y       git       wget       python3       python3-pip       python3-venv       ${extra_packages} &&     apt-get purge --auto-remove -y &&     apt-get clean &&     rm -rf       /tmp/*       /var/lib/apt/lists/*       /var/tmp/*;   elif [ -f /sbin/apk ]; then     apk update &&     apk add --no-cache       git       wget       python3       py3-pip       py3-virtualenv       ${extra_packages} &&     apk del --purge &&     rm -rf       /root/.cache       /tmp/*;   fi &&   mkdir ${SMA_PATH} &&   git config --global --add safe.directory ${SMA_PATH} &&   git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git ${SMA_PATH} &&   python3 -m virtualenv ${SMA_PATH}/venv &&   ${SMA_PATH}/venv/bin/pip install -r ${SMA_PATH}/setup/requirements.txt &&   chgrp users /usr/local/bin/ffmpeg &&   chgrp users /usr/local/bin/ffprobe &&   chmod g+x /usr/local/bin/ffmpeg &&   chmod g+x /usr/local/bin/ffprobe" did not complete successfully: exit code: 1

Thank you for the help btw! Really love your work!

[BastionNtB]

Hey man, not trying to be a pest or anything, just curious if there is any update on this?

Just tried again today and it's still the same error.

[mdhiggins]

Haven't had time til now, but just pushed some updates that should address this issue hopefully

[BastionNtB]

Hey, no worries, and sorry for being pushy. Was just really excited to migrate the service to docker, but I totally get being busy!

Here's the new logs, they were much shorter than last time, but it still seems to give the same-ish error. Different error code.

time="2024-01-19T08:07:21-08:00" level=warning msg="The \"PUID\" variable is not set. Defaulting to a blank string."
time="2024-01-19T08:07:21-08:00" level=warning msg="The \"PGID\" variable is not set. Defaulting to a blank string."
#0 building with "default" instance using docker driver

#1 [sonarr internal] load git source https://github.com/mdhiggins/sonarr-sma.git#build
#1 0.495 7b48929b86181eb48ac04856036fe7136870e188	refs/heads/build
#1 CACHED

#2 [sonarr internal] load metadata for docker.io/jrottenberg/ffmpeg:4.4-ubuntu
#2 DONE 0.4s

#3 [sonarr internal] load metadata for ghcr.io/linuxserver/sonarr:3.0.10
#3 DONE 0.7s

#4 [sonarr ffmpeg 1/2] FROM docker.io/jrottenberg/ffmpeg:4.4-ubuntu@sha256:2fb708065725d08358849344af9ae2e1cea84fbc9aead75c3d6a72af1bdbaee8
#4 DONE 0.0s

#5 [sonarr stage-1 1/6] FROM ghcr.io/linuxserver/sonarr:3.0.10@sha256:4f69472a0cdea29e23967db6a3395487539b759def3920327d1f49ae00b9dfd4
#5 DONE 0.0s

#6 [sonarr ffmpeg 2/2] RUN   mkdir -p /build
#6 CACHED

#7 [sonarr stage-1 2/6] COPY --from=ffmpeg /usr/local/ /usr/local/
#7 CACHED

#8 [sonarr stage-1 3/6] COPY --from=ffmpeg /build /
#8 CACHED

#9 [sonarr stage-1 4/6] RUN   if [ -f /usr/bin/apt ]; then     apt-get update &&     apt-get install -y       git       wget       python3       python3-pip       python3-virutalenv       ${extra_packages} &&     apt-get purge --auto-remove -y &&     apt-get clean &&     rm -rf       /tmp/*       /var/lib/apt/lists/*       /var/tmp/*;   elif [ -f /sbin/apk ]; then     apk update &&     apk add --no-cache       git       wget       python3       py3-pip       py3-virtualenv       ${extra_packages} &&     apk del --purge &&     rm -rf       /root/.cache       /tmp/*;   fi &&   mkdir /usr/local/sma &&   git config --global --add safe.directory /usr/local/sma &&   git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git /usr/local/sma &&   python3 -m virtualenv /usr/local/sma/venv &&   /usr/local/sma/venv/bin/pip install -r /usr/local/sma/setup/requirements.txt
#9 0.608 Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
#9 0.757 Get:2 https://download.mono-project.com/repo/ubuntu stable-focal InRelease [4,416 B]
#9 0.953 Get:3 https://download.mono-project.com/repo/ubuntu stable-focal/main amd64 Packages [46.9 kB]
#9 1.109 Get:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
#9 1.230 Get:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
#9 1.254 Get:6 https://mediaarea.net/repo/deb/ubuntu jammy InRelease [26.1 kB]
#9 1.344 Get:7 http://archive.ubuntu.com/ubuntu jammy/restricted Sources [28.2 kB]
#9 1.351 Get:8 http://archive.ubuntu.com/ubuntu jammy/main Sources [1,668 kB]
#9 1.623 Get:9 http://archive.ubuntu.com/ubuntu jammy/universe Sources [22.0 MB]
#9 1.668 Get:10 https://mediaarea.net/repo/deb/ubuntu jammy/main amd64 Packages [11.6 kB]
#9 2.320 Get:11 http://archive.ubuntu.com/ubuntu jammy/multiverse Sources [361 kB]
#9 2.323 Get:12 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
#9 2.324 Get:13 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1,792 kB]
#9 2.379 Get:14 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
#9 2.401 Get:15 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
#9 2.912 Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Sources [66.9 kB]
#9 2.913 Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/universe Sources [384 kB]
#9 2.921 Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/main Sources [588 kB]
#9 2.952 Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Sources [21.8 kB]
#9 2.953 Get:20 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,624 kB]
#9 2.999 Get:21 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,321 kB]
#9 3.061 Get:22 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1,635 kB]
#9 3.078 Get:23 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [50.4 kB]
#9 3.086 Get:24 http://archive.ubuntu.com/ubuntu jammy-security/restricted Sources [62.9 kB]
#9 3.086 Get:25 http://archive.ubuntu.com/ubuntu jammy-security/multiverse Sources [12.1 kB]
#9 3.097 Get:26 http://archive.ubuntu.com/ubuntu jammy-security/main Sources [307 kB]
#9 3.101 Get:27 http://archive.ubuntu.com/ubuntu jammy-security/universe Sources [227 kB]
#9 3.103 Get:28 http://archive.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [44.6 kB]
#9 3.104 Get:29 http://archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [1,056 kB]
#9 3.156 Get:30 http://archive.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [1,600 kB]
#9 3.191 Get:31 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1,344 kB]
#9 4.402 Fetched 54.6 MB in 4s (13.7 MB/s)
#9 4.402 Reading package lists...
#9 5.573 W: http://download.mono-project.com/repo/ubuntu/dists/stable-focal/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
#9 5.662 Reading package lists...
#9 6.824 Building dependency tree...
#9 7.118 Reading state information...
#9 7.131 E: Unable to locate package python3-virutalenv
#9 ERROR: process "/bin/sh -c if [ -f /usr/bin/apt ]; then     apt-get update &&     apt-get install -y       git       wget       python3       python3-pip       python3-virutalenv       ${extra_packages} &&     apt-get purge --auto-remove -y &&     apt-get clean &&     rm -rf       /tmp/*       /var/lib/apt/lists/*       /var/tmp/*;   elif [ -f /sbin/apk ]; then     apk update &&     apk add --no-cache       git       wget       python3       py3-pip       py3-virtualenv       ${extra_packages} &&     apk del --purge &&     rm -rf       /root/.cache       /tmp/*;   fi &&   mkdir ${SMA_PATH} &&   git config --global --add safe.directory ${SMA_PATH} &&   git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git ${SMA_PATH} &&   python3 -m virtualenv ${SMA_PATH}/venv &&   ${SMA_PATH}/venv/bin/pip install -r ${SMA_PATH}/setup/requirements.txt" did not complete successfully: exit code: 100
------
 > [sonarr stage-1 4/6] RUN   if [ -f /usr/bin/apt ]; then     apt-get update &&     apt-get install -y       git       wget       python3       python3-pip       python3-virutalenv       ${extra_packages} &&     apt-get purge --auto-remove -y &&     apt-get clean &&     rm -rf       /tmp/*       /var/lib/apt/lists/*       /var/tmp/*;   elif [ -f /sbin/apk ]; then     apk update &&     apk add --no-cache       git       wget       python3       py3-pip       py3-virtualenv       ${extra_packages} &&     apk del --purge &&     rm -rf       /root/.cache       /tmp/*;   fi &&   mkdir /usr/local/sma &&   git config --global --add safe.directory /usr/local/sma &&   git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git /usr/local/sma &&   python3 -m virtualenv /usr/local/sma/venv &&   /usr/local/sma/venv/bin/pip install -r /usr/local/sma/setup/requirements.txt:
3.086 Get:25 http://archive.ubuntu.com/ubuntu jammy-security/multiverse Sources [12.1 kB]
3.097 Get:26 http://archive.ubuntu.com/ubuntu jammy-security/main Sources [307 kB]
3.101 Get:27 http://archive.ubuntu.com/ubuntu jammy-security/universe Sources [227 kB]
3.103 Get:28 http://archive.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [44.6 kB]
3.104 Get:29 http://archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [1,056 kB]
3.156 Get:30 http://archive.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [1,600 kB]
3.191 Get:31 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1,344 kB]


7.131 E: Unable to locate package python3-virutalenv
------
failed to solve: process "/bin/sh -c if [ -f /usr/bin/apt ]; then     apt-get update &&     apt-get install -y       git       wget       python3       python3-pip       python3-virutalenv       ${extra_packages} &&     apt-get purge --auto-remove -y &&     apt-get clean &&     rm -rf       /tmp/*       /var/lib/apt/lists/*       /var/tmp/*;   elif [ -f /sbin/apk ]; then     apk update &&     apk add --no-cache       git       wget       python3       py3-pip       py3-virtualenv       ${extra_packages} &&     apk del --purge &&     rm -rf       /root/.cache       /tmp/*;   fi &&   mkdir ${SMA_PATH} &&   git config --global --add safe.directory ${SMA_PATH} &&   git clone https://github.com/mdhiggins/sickbeard_mp4_automator.git ${SMA_PATH} &&   python3 -m virtualenv ${SMA_PATH}/venv &&   ${SMA_PATH}/venv/bin/pip install -r ${SMA_PATH}/setup/requirements.txt" did not complete successfully: exit code: 100

Here is the compose:

services:
  sonarr:
    container_name: sonarr
    hostname: sonarr
    #image: mdhiggins/sonarr-sma:latest
    build:
      context: https://github.com/mdhiggins/sonarr-sma.git#build
      args:
        #- ffmpeg_tag=4.3-alpine312
        - sonarr_tag=3.0.10
    runtime: nvidia # Expose NVIDIA GPUs
    restart: always
    networks:
      - reverseproxy-network
    ports:
      - 8989:8989
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - SMA_HWACCEL=true
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
      - NVIDIA_VISIBLE_DEVICES=all
      - UMASK=0002
    volumes:
      - /opt/sonarr-config:/config
      - /opt/sonarr-sma-config:/usr/local/sma/config
      - sharev2:/nfs/share

volumes:
  sharev2:
    external: true
networks:
  reverseproxy-network:
    external: true

[mdhiggins]

Turns out spelling is hard

Just pushed and update that spells virtual correctly

[BastionNtB]

Successful building! Thank you!

However, I'm now having issues with ffmpeg.

ffmpeg
ffmpeg: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

[mdhiggins]

Does installing the openssl package inside the container fix that?

[BastionNtB]

Looks like it's already installed

root@sonarr:/# apt install openssl -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
openssl is already the newest version (3.0.2-0ubuntu1.12).
openssl set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@sonarr:/# ffmpeg
ffmpeg: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

root@sonarr:/# apt info openssl
Package: openssl
Version: 3.0.2-0ubuntu1.12
Status: install ok installed
Priority: optional
Section: utils
Maintainer: Ubuntu Developers <[email protected]>
Original-Maintainer: Debian OpenSSL Team <[email protected]>
Installed-Size: 2,102 kB
Depends: libc6 (>= 2.34), libssl3 (>= 3.0.2-0ubuntu1.2)
Suggests: ca-certificates
Homepage: https://www.openssl.org/
Download-Size: unknown
APT-Manual-Installed: yes
APT-Sources: /var/lib/dpkg/status
Description: Secure Sockets Layer toolkit - cryptographic utility
 This package is part of the OpenSSL project's implementation of the SSL
 and TLS cryptographic protocols for secure communication over the
 Internet.
 .
 It contains the general-purpose command line binary /usr/bin/openssl,
 useful for cryptographic operations such as:
  * creating RSA, DH, and DSA key parameters;
  * creating X.509 certificates, CSRs, and CRLs;
  * calculating message digests;
  * encrypting and decrypting with ciphers;
  * testing SSL/TLS clients and servers;
  * handling S/MIME signed or encrypted mail.

root@sonarr:/# ldd /usr/bin/openssl
        linux-vdso.so.1 (0x00007fff7f3b8000)
        libssl.so.3 => /usr/lib/x86_64-linux-gnu/libssl.so.3 (0x00007fe466b4e000)
        libcrypto.so.3 => /usr/lib/x86_64-linux-gnu/libcrypto.so.3 (0x00007fe46670c000)
        libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x00007fe4664e3000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fe466cf0000)

Just running around doing some searches on the error itself, some people ran some commands which showed some information for them, I've included them up above. it seems that there is a libssl.so.3 shown in some of the commands, but not a libssl.so.1.1 as it's looking for. Unless I'm misunderstanding something, is this something recent with the ffmpeg build or do I need to install a specific version of openssl or something?

I tried making a symlink like so, as someone else suggested, but it didn't fix the issue.

root@sonarr:/# cd /usr/local/lib
root@sonarr:/usr/local/lib# ln -s libssl.so.3 libssl.so.1.1
root@sonarr:/usr/local/lib# ffmpeg
ffmpeg: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

[mdhiggins]

Hm maybe libssl-dev is the missing package?

[BastionNtB]

I tried to install it, but it said no package could be found.

[mdhiggins]

Hm you're on an ubuntu based image? I fired up a quick jammy instance and I'm able to find the package on there

[BastionNtB]

This is using the sonarr docker imaging from the custom build from the sonarr-sma build context. I've set the sonarr tag to sonarr_tag=3.0.10 which is the ubuntu version.

Here's what I get when I try to install it:

root@sonarr:/# apt install libssl-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package libssl-dev

Here is the distro I'm running the command on.

root@sonarr:/# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"

When I do a search for libssl, here is the only package it can find.

root@sonarr:/# apt search libssl
Sorting... Done
Full Text Search... Done
libssl3/now 3.0.2-0ubuntu1.10 amd64 [installed,local]
  Secure Sockets Layer toolkit - shared libraries

[mdhiggins]

https://packages.ubuntu.com/jammy/all/allpackages

libssl-dev is part of the security repo, make sure you have that in your sources

cat /etc/apt/sources.list /etc/apt/sources.list.d/*

[BastionNtB]

This is getting a little out of my area, here is what repositories I have when I run that command.

root@sonarr:/# cat /etc/apt/sources.list /etc/apt/sources.list.d/*
deb http://archive.ubuntu.com/ubuntu/ jammy main restricted
deb-src http://archive.ubuntu.com/ubuntu/ jammy main restricted
deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
deb http://archive.ubuntu.com/ubuntu/ jammy universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ jammy universe multiverse
deb http://archive.ubuntu.com/ubuntu/ jammy-updates universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates universe multiverse
deb http://archive.ubuntu.com/ubuntu/ jammy-security main restricted
deb-src http://archive.ubuntu.com/ubuntu/ jammy-security main restricted
deb http://archive.ubuntu.com/ubuntu/ jammy-security universe multiverse
deb-src http://archive.ubuntu.com/ubuntu/ jammy-security universe multiverse
deb https://mediaarea.net/repo/deb/ubuntu jammy main
deb http://download.mono-project.com/repo/ubuntu stable-focal main

It looks to me like the image has jammy-security main restricted, as well as jammy-security universe multiverse, unless I'm misunderstanding something.

https://packages.ubuntu.com/jammy/security/libssl-dev

[mdhiggins]

You are running apt update before trying to run these installs correct?

[BastionNtB]

Sorry for the late response. I was not running apt update. However, after running apt update, it found the package, but ffmpeg still does not work, nor does it work after updating openssl.

I've started from scratch again trying to get it working, but to no avail. I'm at a total loss, I don't know what else to try to get this to work, and I don't know where to go from here. How is anyone else getting ffmpeg to work after lsio updated to Alpine?

Here is my compose file.

services:
  sonarr:
    container_name: sonarr
    hostname: sonarr
    build:
      context: https://github.com/mdhiggins/sonarr-sma.git#build
      args:
        - ffmpeg_tag=5.0.1-ubuntu2004
        - sonarr_tag=3.0.10
    runtime: nvidia # Expose NVIDIA GPUs
    restart: always
    networks:
      - reverseproxy-network
    ports:
      - 8989:8989
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - SMA_HWACCEL=true
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
      - NVIDIA_VISIBLE_DEVICES=all
      - SMA_EXTRA_PACKAGES=libssl-dev
      - UMASK=0002
    volumes:
      - /opt/sonarr-config:/config
      - /opt/sonarr-sma-config:/usr/local/sma/config

networks:
  reverseproxy-network:
    external: true

[mdhiggins]

I have a suspicion that no one has gotten ffmpeg working on alpine with nvidia hardware acceleration
Most people either don't use hardware or use quicksync

What errors were you having on the older builds after installing the missing packages

If you sort it out or find a solution let me know I'd be happy to integrate it

[BastionNtB]

Damn, that's unfortunate. What about switching the base image to hotio's sonarr? I don't know if they switched to alpine or not though.

As for the error, If I try to run ffmpeg, it's the same error as before when I opened this

ffmpeg
ffmpeg: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Installing the libssl-dev and updating openssl made no difference.

Edit:

Followed this and now ffmpeg works........ !

https://gist.github.com/joulgs/c8a85bb462f48ffc2044dd878ecaa786

However, no hwaccels :(

ffmpeg -hide_banner -hwaccels
Hardware acceleration methods:

[mdhiggins]

Is this going back to the "build" tag? Cause if you use the old version (pre alpine) plus the nvidia build tag I would think it should work

[BastionNtB]

Yeah it was, and I did end up switching to the nvidia ffmpeg, but it's giving me a whole other error now.

ffmpeg
ffmpeg: error while loading shared libraries: libnppig.so.11: cannot open shared object file: No such file or directory

And this library seems to be tied directly with nvidia somehow and they don't really offer the install of it.

Here is my compose

services:
  sonarr:
    container_name: sonarr
    hostname: sonarr
    #image: mdhiggins/sonarr-sma:latest
    build:
      context: https://github.com/mdhiggins/sonarr-sma.git#build
      args:
        - ffmpeg_tag=4.4.1-nvidia2004
        - sonarr_tag=3.0.10
    runtime: nvidia # Expose NVIDIA GPUs
    restart: always
    networks:
      - reverseproxy-network
    ports:
      - 8989:8989
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - SMA_HWACCEL=true
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
      - NVIDIA_VISIBLE_DEVICES=all
      - SMA_EXTRA_PACKAGES=libssl-dev 
      - UMASK=0002
    volumes:
      - /opt/sonarr-config:/config
      - /opt/sonarr-sma-config:/usr/local/sma/config
    devices:
      - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes

[wdckwrth]

I used your compose and then the gist to get the ssl library. The error you are getting now was solved in this ticket.

You need to add this to your environment in your compose file:

LD_LIBRARY_PATH=/usr/local/cuda-11.4/lib64

After I did I got:

ffmpeg -hide_banner -hwaccels
Hardware acceleration methods:
cuda

I was then able to use manual.py to run a transform.

cuda hwaccel is supported by this ffmpeg build and will be used [hwaccels].
[snip]
/usr/local/bin/ffmpeg -init_hw_device cuda=sma:0 -hwaccel_device sma -hwaccel cuda -hwaccel_output_format cuvid

[BastionNtB]

Thank you for the contribution... You got it working for me! Thank you!

[Converter]
ffmpeg = ffmpeg
ffprobe = ffprobe
threads = 0
hwaccels = cuda
hwaccel-decoders = h264_cuvid, hevc_cuvid, av1_cuvid, vc1_cuvid, vp8_cuvid, vp9_cuvid, mjpeg_cuvid, mpeg1_cuvid, mpeg2_cuvid, mpeg4_cuvid
hwdevices = 
hwaccel-output-format =

This is what I ended up with for the converter config. Couldn't get it working with cuda:cuda set for the hwaccel-output-format like you had set.

Here is my final compose that is currently working.

services:
  sonarr:
    container_name: sonarr
    hostname: sonarr
    build:
      context: https://github.com/mdhiggins/sonarr-sma.git#build
      args:
        - ffmpeg_tag=5.1-nvidia2004
        - sonarr_tag=3.0.10
    runtime: nvidia # Expose NVIDIA GPUs
    restart: always
    ports:
      - 8989:8989
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - SMA_HWACCEL=true
      - NVIDIA_DRIVER_CAPABILITIES=all
      - NVIDIA_VISIBLE_DEVICES=all
      - UMASK=0002
      - LD_LIBRARY_PATH=/usr/local/cuda-11.4/lib64
    volumes:
      - /opt/sonarr-config:/config
      - /opt/sonarr-sma-config:/usr/local/sma/config
    devices:
      - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes

I did have to use the gist here https://gist.github.com/joulgs/c8a85bb462f48ffc2044dd878ecaa786 to get the library. This is unfortunately using Ubuntu, and thus the older version of Sonarr... But nvidia is the one that isn't supporting alpine at the moment so... Yeah. Best that we can do at the moment.

[mdhiggins]

mdhiggins/sonarr-sma#57 (comment)

Made lots of changes to help with nvidia for the containers and allow people to use the older versions using the #build-s6v2 tags if anyone needs to reference