[Bug]: 'dev' docker images no longer start from commit 7031c47f (02/06/2024 15:47)

[ubawurinna]

Describe the problem you are having

Docker image startup log complains about tempio command not found
Docker image startup log

[INFO] Starting NGINX...
./run.user: line 84: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
[INFO] Service NGINX exited with code 127 (by signal 0)

The tempio command is called from a nginx script
docker/main/rootfs/etc/s6-overlay/s6-rc.d/nginx/run

# build templates for optional TLS support
python3 /usr/local/nginx/get_tls_settings.py | \
    tempio  -template /usr/local/nginx/templates/listen.gotmpl \
            -out /usr/local/nginx/conf/listen.conf

The problem is due to the fact that the tempio command folder is not in the PATH.
Bash inside docker

echo ${PATH}
/usr/lib/btbn-ffmpeg/bin:/usr/local/go2rtc/bin:/usr/local/nginx/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

But the tempio command folder is defined in the PATH in the Dockerfile
docker/main/Dockerfile

ENV PATH="/usr/lib/btbn-ffmpeg/bin:/usr/local/go2rtc/bin:/usr/local/tempio/bin:/usr/local/nginx/sbin:${PATH}"

I don't know why the tempio command folder is no longer defined in PATH once the docker image has been created.
The Docker images come from the URL ghcr.io/blakeblackshear/frigate:dev-xxxxxxx
If the tempio command is called with the full path in the nginx script, the docker image starts.

Steps to reproduce

run docker image dev-7031c47 or later

Version

0.14.0-0d862d6

Frigate config file

Useless

Relevant log output

[INFO] Starting NGINX...
./run.user: line 84: tempio: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
[INFO] Service NGINX exited with code 127 (by signal 0)

Operating system

Debian

Install method

Docker Compose

Network connection

Wireless

Camera make and model

Tapo C510W

Any other information that may be helpful

No response

[hawkeye217]

This is probably a duplicate of #11755

Are you using Portainer?

[ubawurinna]

yes it's totally a duplicate.
Same problem, same solution.
Destroy the portainer frigate stack and recreate from scratch