-
-
Notifications
You must be signed in to change notification settings - Fork 213
BUG: Unable to fully change ports running in host mode #1472
New issue
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
Comments
Full logs for default case:
|
When I run the docker container I hav been pulling the environment out of the mediamtx task and it seems like stuff is getting across correctly. With my custom run this command yields:
So I would think MTX is correctly setup |
It looks like In I tested a fix by copying Then, shut down the stack with Next, edit In
Bring the stack back up with Watch the logs with
I think modifying |
Describe the bug
Based on the existing issue regarding the IOCTL stuff its recommended to run in
networking_mode=host
The issue I have is my frigate instance is on the same box and there are port-conflicts.If I'm running solo and leaving things as-is with defaults I can get a successful hit with
ffprobe
Following the directions here:
https://github.com/mrlt8/docker-wyze-bridge/wiki/Advanced-Option#mediamtx
I'm trying to rewrite all my ports.
Base case (no options)
Using this
docker-compose.yaml
with all the custom stuff commented outFirst I startup then I can see the streams are up:
docker-compose logs | grep up
Next using
ffprobe
we can hit a stream which is greatCustom Ports
my
.env
file defines the following:And this time we uncomment stuff in our
docker-compose
First difference is that:
It doesnt seem like the cameras auto-start in this configuraiton. The full log is here:
And rightfully so I think the RTSP failes:
Am I missing an
ENV_VAR
or something?Affected Bridge Version
v2.10.3
Bridge type
Docker Run/Compose
Affected Camera(s)
No response
Affected Camera Firmware
No response
docker-compose or config (if applicable)
The text was updated successfully, but these errors were encountered: