Bind address for Talk container recently reverted to 0.0.0.0

[Curtingham]

I've had Nextcloud AIO up and running for months using a specified bind address via the APACHE_IP_BINDING environment variable. Until recently, this environment variable seemed to also apply to the IP address bound for the nextcloud-aio-talk container.

This was desirable functionality, as it let me run other containers on the same host that use the same port (by allowing me to bind those containers to different IP aliases). In the past couple days, this has reverted to binding to all network addresses (0.0.0.0).

I deployed a test server and set up a test Nextcloud AIO instance following a similar procedure as my live environment. My deploy command looks like this:

sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 10.1.1.15:8080:8080 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
--env APACHE_PORT=11000 \
--env APACHE_IP_BINDING=10.1.1.15 \
ghcr.io/nextcloud-releases/all-in-one:latest \

In my example, 10.1.1.11 is the host's standard IP address, and 10.1.1.15 is an IP address alias I added.

The output of docker ps --all --format 'table {{.ID}}\t{{.Names}}\t{{.Ports}}' is as follows (after having removed irrelevant containers):

NAMES                               PORTS
nextcloud-aio-apache                80/tcp, 10.1.1.15:11000->11000/tcp
nextcloud-aio-mastercontainer       80/tcp, 8443/tcp, 9000/tcp, 10.1.1.15:8080->8080/tcp
nextcloud-aio-talk                  0.0.0.0:3478->3478/tcp, 0.0.0.0:3478->3478/udp, [::]:3478->3478/tcp, [::]:3478->3478/udp

Is anyone able to confirm if this is an expected change, and if so, is there any way to specify what IP address AIO will use to bind the nextcloud-aio-talk container? Thanks in advance for any insight!

[Zoey2936]

From what I remember it never applied to the talk port

[szaimen]

indeed 👍

[szaimen]

@Curtingham what you can do is to adjust the talk port. See https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-adjust-the-talk-port

[Curtingham]

Thank you both for confirming! I could swear this was working differently before, but as a test I restored a VM backup from a couple weeks ago and the talk container shows 0.0.0.0 then as well.

It's a mystery how my setup was seemingly working until a couple days ago. I even checked my Icinga monitoring system history, and it shows both the Talk container, and the other container I have running on 3478, up at the same time. But that's all pretty much a moot point - I'll just reconfigure the Talk container to run on a different port as you suggested.

Thanks again!