rpos as a docker image

[hardysim]

I'm trying to run rpos as a docker container and using my Dockerfile from #133 (comment) to create the image. This is working when using the "host network" when running the container but not when trying to open just the ports needed.

I've did some research and found port 3702 UDP to be used to discover ONVIF and netstat also shows ports 5353 UDP and 8081 TCP to be opened when running rpos directly on the host. But adding all those ports to the docker container doesn't work.

Which ports are needed to run / discover rpos? Can we get a working docker image / configuration (maybe to be used with docker compose)?

I'd like to combine rpos as a proxy for mediamtx inside a single docker compose file (to stream from my GoPro). And if I'm right, rpos is only needed once to discover the actual RTSP stream so it could be stopped once the initial discovery is done?

[uglurass]

If you don't care about security you can always have api run as a background port for it.

…

On Tue, Dec 30, 2025, 09:39 Simon Hardt ***@***.***> wrote: *hardysim* created an issue (BreeeZe/rpos#181) <#181> I'm trying to run rpos as a docker container and using my Dockerfile from #133 (comment) <#133 (comment)> to create the image. This is working when using the "host network" when running the container but not when trying to open just the ports needed. I've did some research and found port 3702 UDP to be used to discover ONVIF and netstat also shows ports 5353 UDP and 8081 TCP to be opened when running rpos directly on the host. But adding all those ports to the docker container doesn't work. Which ports are needed to run / discover rpos? Can we get a working docker image / configuration (maybe to be used with docker compose)? I'd like to combine rpos as a proxy for mediamtx inside a single docker compose file (to stream from my GoPro). And if I'm right, rpos is only needed once to discover the actual RTSP stream so it could be stopped once the initial discovery is done? — Reply to this email directly, view it on GitHub <#181>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGQVSNZMRDDRRYZXFWJ6RN34EJB5PAVCNFSM6AAAAACQJUZJHWVHI2DSMVQWIX3LMV43ASLTON2WKOZTG43DSNRTGMYDGOI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[hardysim]

Not sure what you mean by that. Could you explain a little more? My goal is to run rpos as a docker container but it seems I need to pass through some ports - but which exactly?

Using the container with the host network is working so it should be possible if I know what to pass through?

[RogerHardiman]

3702 being for ONVIF discovery and ONVIF viewing software (NVRs, VMS, CCTV software) use it once to find the "ONVIF Camera" on the LAN.
Then ONVIF viewing software (or a NVR) uses ONVIF Protocol via port 8081 to request the current RTSP URL for the video, and this is where the MediaMTX RTSP URL would be sent to the ONVIF viewing software.
Some ONVIF Viewing software is happy with a RTSP URL on another IP address. Some software will expect it to be the same IP Address that RPOS was accessed from.

[RogerHardiman]

port 5353 is not part of RPOS