We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While the pulled image works great
docker pull alfg/nginx-rtmp docker run -it -p 1935:1935 -p 8080:80 --rm alfg/nginx-rtmp
the image built from the source (v1.6.0) does not:
docker build -t nginx-rtmp . docker run -it -p 1935:1935 -p 8080:80 --rm nginx-rtmp
When I try to stream from OBS I got this logged:
2023/09/05 17:59:12 [info] 11#11: *1 exec: starting managed child 'ffmpeg', client: 192.168.1.23, server: [0.0.0.0:1935](http://0.0.0.0:1935/) 2023/09/05 17:59:12 [notice] 11#11: signal 17 (SIGCHLD) received from 13 2023/09/05 17:59:12 [alert] 11#11: unknown process 13 exited on signal 11 2023/09/05 17:59:13 [info] 11#11: *1 exec: child 13 exited; ignoring, client: 192.168.1.23, server: [0.0.0.0:1935](http://0.0.0.0:1935/) 2023/09/05 17:59:13 [info] 11#11: *1 exec: terminating child 13, client: 192.168.1.23, server: [0.0.0.0:1935](http://0.0.0.0:1935/)
Any help is appreciated.
The text was updated successfully, but these errors were encountered:
We have the same issue. Would love to hear a solution
Sorry, something went wrong.
Same here!
Seems like a segmentation error with ffmepg that happens during the build process.
We removed the build ffmpeg build part from the Dockerfile.
And just added it with apk add
RUN apk add --no-cache \ ca-certificates \ gettext \ openssl \ pcre \ lame \ libogg \ curl \ libass \ libvpx \ libvorbis \ libwebp \ libtheora \ opus \ rtmpdump \ x264-dev \ x265-dev \ ffmpeg
No branches or pull requests
While the pulled image works great
the image built from the source (v1.6.0) does not:
When I try to stream from OBS I got this logged:
Any help is appreciated.
The text was updated successfully, but these errors were encountered: