Trying to start the 1.4.0 container, I get this error:
$ podman run docker.io/testcontainers/vnc-recorder:1.4.0
Error: crun: executable file `flvrec.py` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
In contrast, 1.3.0 shows me the help message:
$ podman run docker.io/testcontainers/vnc-recorder:1.3.0
/usr/local/bin/flvrec.py 20100207
usage: /usr/local/bin/flvrec.py [-d] [-q] [-o filename] [-r framerate] [-K keyframe] [-e vnc_encoding] [-P vnc_pwdfile] [-N] [-B blocksize] [-C clipping] [-S subprocess] [host[:display] [port]]
Poking around inside the containers,
- in 1.3.0,
flvrec.py is in /usr/local/bin, which is on root's PATH
- in 1.4.0,
flvrec.py is in /root/.local/bin, which isn't on root's PATH
- looking at
/etc/skel/.profile (the template .profile when users are created), $HOME/.local/bin is added to the PATH for any newly created users, but root's .profile doesn't add it
- this file is actually a symlink to
/root/.local/pipx/venvs/vnc2flv3/bin/flvrec.py
So it looked like something changed where doing pipx install now puts the installed scripts in a place which isn't on the PATH for the root user.
Trying to start the 1.4.0 container, I get this error:
In contrast, 1.3.0 shows me the help message:
Poking around inside the containers,
flvrec.pyis in/usr/local/bin, which is on root's PATHflvrec.pyis in/root/.local/bin, which isn't on root's PATH/etc/skel/.profile(the template.profilewhen users are created),$HOME/.local/binis added to the PATH for any newly created users, but root's.profiledoesn't add it/root/.local/pipx/venvs/vnc2flv3/bin/flvrec.pySo it looked like something changed where doing
pipx installnow puts the installed scripts in a place which isn't on the PATH for the root user.