You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not possible to signal the ffmpeg process inside the container (probably because of the wrapper shell script).
This is required for cleanly terminating ffmpeg inside the container (and the container) itself (ffmpeg handling disconnections, etc.).
Expected Behavior
Process signals correctly passed to ffmpeg process inside container.
Steps To Reproduce
Start a container from linuxserver/ffmpeg image.
Use docker kill to send a signal to ffmpeg to cleanly shut down.
Note that the signal is not handled, ffmpeg and the container continues running.
Attach shell in running container.
Send termination signal using Ctrl + c, note that it is not handled by ffmpeg but by shell script/Docker instead.
Environment
- OS: `Ubuntu 22.04.5 LTS`- How docker service was installed: By official `docker` package.
Docker creation
Default docker run test command.
Container logs
got 3 SIGTERM/SIGINTs, forcefully exiting
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
It is not possible to signal the
ffmpeg
process inside the container (probably because of the wrapper shell script).This is required for cleanly terminating
ffmpeg
inside the container (and the container) itself (ffmpeg
handling disconnections, etc.).Expected Behavior
Process signals correctly passed to
ffmpeg
process inside container.Steps To Reproduce
linuxserver/ffmpeg
image.docker kill
to send a signal toffmpeg
to cleanly shut down.ffmpeg
and the container continues running.Ctrl
+c
, note that it is not handled byffmpeg
but by shell script/Docker instead.Environment
Docker creation
Default docker run test command.
Container logs
The text was updated successfully, but these errors were encountered: