Then you are unaffected.
Is there any easy way to do that for multiple containers?
I can modify the run.sh script for each container, but it needs to be in place before the container starts.
Only way I can think of is to create the container, docker cp the modified run.sh script to it and start the container. But would have to remember do this every time I pull a new image.
For the first container, add -v container1-run.sh:/run.sh to its command line (or equivalent in the compose file). For the second container, -v container2-run.sh:/run.sh, and so on and so forth for each container.
(If you're running multiple containers and familiar with OCI/Docker, this shouldn't be new information.)
@chDVRuser Are you running those containers on a Synology or other platform with the broken iptables setup?
Synology DSM 7.2.1-69057 Update 3
1 Like
Thanks. I wasn't aware you could volume mount a single file like that.
I’ll look at adding an environment variable to the docker file for specify a local port.
1 Like
"Volume" is a misnomer ... it's merely an overlay, whether that be an entire directory, or a single file.
2 Likes
Hopefully before this becomes a stable release 
@chDVRuser Please pull the latest docker image. There is a new CHANNELS_PORT environment variable you can use to specify an alternate port.
Thanks. Updated all container and server versions.
I'm good to go. Not sure about all the rest of the users affected.
@chDVRuser Just to make sure I understand the situation, were all of your DVRs blocked from local access when you updated until you made the networking change?
1 Like
I didn't update Pre-Release until I pulled the new docker image. I read these posts and said "Not me. I'm not jumping in with my eyes closed".
I'm assuming this affects older docker daemon versions and not sure which versions work or don't.
Just reverted one of my docker container servers on my Synology to using a named bridge network.
It's prompting for an Authorization Code when accessed via local IP address.
Log shows
2024/01/05 17:34:21.325341 [HTTP] Detected docker guest gateway. Requiring authentication for: 172.18.0.1
1 Like
I experienced this and was able to authenticate locally, but
what does this mean. You can't connect or authenticate using a local client?
Locally, clients do not use authentication. So, if the server is rejecting local requests, then the clients will not be able to connect.
1 Like
Having issues with my dockers running under Windows 11 and WSL2 but those on ubuntu the network: host option had no issues
Are you seeing this in the DVR log when you try to connect?
All I see is Running Channels DVR..
However unlike with -p option I don't see the port listening with the network: host command
In doing research I've read where someone stated "If you want host networking, you can uninstall Docker Desktop, and install Docker Engine natively inside WSL2" so may need to try that instead
1 Like