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
Describe the bug
Device used : Raspberry pi 5 8GB
I pulled docker image by my raspberry pi with image ossrs/srs-stack:5 and try to use forwarding function included but seeing not forwarding and the status changing between forwarding and waiting.
So I try to docker logs srs-stack
and it show "segmentation fault" between the logs
So I tried to enter the docker by docker exec -it srs-stack /bin/bash
and run root@437e8b8235bf:/usr/local/srs-stack/platform# ffmpeg Segmentation fault
so it seems to be broken with ffmpeg binary.
Version
srs-stack:5 on Raspberry pi 5 8GB
To Reproduce
Steps to reproduce the behavior:
Run on raspberry pi 5 docker run --restart always -d -it --name srs-stack -v $HOME/data:/data -p 2022:2022 -p 2443:2443 -p 1935:1935 -p 8000:8000/udp -p 10080:10080/udp ossrs/srs-stack:5
Describe the bug
Device used : Raspberry pi 5 8GB
I pulled docker image by my raspberry pi with image ossrs/srs-stack:5 and try to use forwarding function included but seeing not forwarding and the status changing between forwarding and waiting.
So I try to
docker logs srs-stack
and it show "segmentation fault" between the logs
So I tried to enter the docker by
docker exec -it srs-stack /bin/bash
and run
root@437e8b8235bf:/usr/local/srs-stack/platform# ffmpeg
Segmentation fault
so it seems to be broken with ffmpeg binary.
Version
srs-stack:5 on Raspberry pi 5 8GB
To Reproduce
Steps to reproduce the behavior:
docker run --restart always -d -it --name srs-stack -v $HOME/data:/data -p 2022:2022 -p 2443:2443 -p 1935:1935 -p 8000:8000/udp -p 10080:10080/udp ossrs/srs-stack:5
docker exec -it srs-stack /bin/bash
root@437e8b8235bf:/usr/local/srs-stack/platform# ffmpeg
Segmentation fault
Expected behavior
FFmpeg should run fine to make forwarding feature to successfully forwarded
Screenshots
The text was updated successfully, but these errors were encountered: