Open awdm opened 1 year ago
same here
Same issue here. I don't know why.
Aha! This is disappointing: https://stackoverflow.com/questions/35586778/docker-container-doesnt-expose-ports-when-net-host-is-mentioned-in-the-docker
The host networking driver only works on Linux hosts, and is not supported on Docker for Mac, Docker for Windows, or Docker EE for Windows Server.
Here's the command that works for me in windows:
docker run -p 8083:8083 -d --name rtsp-to-web ghcr.io/deepch/rtsptoweb:latest
I added the -d to detach from the command line, but that's optional.
After the initial run, if you want to use the same container, this command works:
docker start rtsp-to-web
Here's the command that works for me in windows:
docker run -p 8083:8083 -d --name rtsp-to-web ghcr.io/deepch/rtsptoweb:latest
I added the -d to detach from the command line, but that's optional.After the initial run, if you want to use the same container, this command works:
docker start rtsp-to-web
this works for me on Windows too.
@WhiteHatRootkitJedi But you can set Docker to Linux mode on a Windows machine. Shouldn't that resolve this issue? Also, does WebRTC work when you use that command?
I followed the instructions in the Readme to launch the application through Docker. I mounted a config file and there are no error messages. But when I open 127.0.0.1:8083 the webpage doesn't open. Is there any additional configuration I need to do that isn't documented?
Edit: I am aware that you can add
EXPOSE 8083
in the Dockerfile and then run the image with-p 8083:8083
and without--network host
. While this technically makes the frontend show up, it's not fully functional and as such not an option for me.