[BUG] ffprobe is not in PATH on ARM images (aarch64/armhf)

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Follow-up on this closed report : [BUG] ffprobe not available #319

The ffprobe binary is included in the docker image BUT is not in the system $PATH - that;s why its not working. Has nothing to do with Sonarr (also broken in Radarr docker image). It's the docker image itself. This breaks internal functions that rely on it.

1. App Log Proof: Application Errors confirm it's not working in the *arr Log - The apps themselves can't find ffprobe for their internal tasks:
   --log:
   |Error|DetectSample|Failed to get runtime from the file, make sure ffprobe is available
   |Error|DetectSample|Failed to get runtime from the file, make sure ffprobe is available
   ...etc..

2. Proof from the Container Shell:

# docker exec -it sonarr /bin/bash
# ffprobe -version
bash: ffprobe: command not found

# which ffprobe
# echo $PATH
/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

# ls -al /app/sonarr/bin/ffprobe
-rwxr-xr-x 1 1001 118 12434136 Jun 21 02:48 /app/sonarr/bin/ffprobe

# /app/sonarr/bin/ffprobe  -version
ffprobe version 5.1.4 Copyright (c) 2007-2023 the FFmpeg developers

...etc...

3. Suggested Fix (symlink method) - path'ed correctly:
   This could be resolved by adding a symlink from the binary's location to a directory in the PATH, for example:
   Dockerfile: eg
   ln -s /app/sonarr/bin/ffprobe /usr/local/bin/ffprobe

---

Or add the path OR install it standardly within the docker image.

That way it would make the tool available system-wide within the container and perm fix the issue. Same with any other incorrectly installed apps in the container that are not in the path.

Thanks

Expected Behavior

No response

Steps To Reproduce

1. Enable within *arr (ffprobe)
2. Check *arr logs for error
3. Confirm issue in docker container:

# docker exec -it sonarr /bin/bash
# ffprobe -vesion
bash: ffprobe: command not found

# which ffprobe
# echo $PATH
/lsiopy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

# ls -al /app/sonarr/bin/ffprobe
-rwxr-xr-x 1 1001 118 12434136 Jun 21 02:48 /app/sonarr/bin/ffprobe

# /app/sonarr/bin/ffprobe  -version
ffprobe version 5.1.4 Copyright (c) 2007-2023 the FFmpeg developers

Environment

- OS: DietPi (latest)
- How docker service was installed:

CPU architecture

arm64

Docker creation

docker run -d \
  --name=sonarr \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -p 8989:8989 \
  -v /mnt/dietpi_userdata/.config/sonarr/data:/config \
  -v /mnt/tvseries:/tv `#optional` \
  -v /mnt/downloadclient-downloads:/downloads `#optional` \
  --restart unless-stopped \
  lscr.io/linuxserver/sonarr:latest

Container logs

|Error|DetectSample|Failed to get runtime from the file, make sure ffprobe is available
|Error|DetectSample|Failed to get runtime from the file, make sure ffprobe is available

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

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

[Fursje]

This also seems to be the case with amd64:latest
Failed to get runtime from the file, make sure ffprobe is available

[aptalca]

Sonarr knows where it is and can access it. It doesn't need to be in the system PATH.

The error does not say ffprobe is not available. It says it can't get the runtime. The second part is just a suggestion.