Additional/second IP for XIBO-Docker

I’m using the docker-image of XIBO 1.8.2 on my Suse 42.3.
This Suse is running as a VirtualBox-machine with two NICs (host system ist Win10pro with two NICs).
ifconfig in the virtual machine shows:
inet addr: Bcast: Mask:
inet addr: Bcast: Mask:
inet addr: Bcast: Mask:
inet addr: Bcast: Mask:

First problem (perhaps not) a xibo-problem:
How can I change the br-… IP, because it conficts with eth1-IP-adress and subnet which I can’t change, because it’s a DHCP-adress.

Running (as root):

xiboserver:~ # docker network inspect xibo_default
“Name”: “xibo_default”,
“Id”: “A_LONG_ID_”,
“Created”: “2017-10-11T12:18:24.868804358+02:00”,
“Scope”: “local”,
“Driver”: “bridge”,
“EnableIPv6”: false,
“IPAM”: {
“Driver”: “default”,
“Options”: null,
“Config”: [
“Subnet”: “”,
“Gateway”: “”

How can I change the subnet?

Second problem:
The XIBO-Webinterface listens on (port 80) and works normally.
But trying to access Xibo-Webinterface on eth1 ( fails, i.e. the apache didn’t answer on this ip.
Thanks for any hints.
Best regards

You can customise your docker-compose file by adding to the bottom:

        - subnet:

Then down and up the containers to apply.

Once you resolve the first issue, the second will work. By default, the CMS containers bind to all interfaces on the ports you’ve defined. It’s not working currently because of the routing issue related to your network interfaces.

Hi Alex,
thank you very, very much.
It could be so easy :wink:

I’m new to containers and I didn’t found any hints in the xibo-doc, so this should be a FAQ or a short hint in the install docs.

Thanks again und bye

I think it’s very unlikely that people will have a clash of IPs. You’re the first in the 7 months since the 1.8 release, so I don’t think it counts as frequently asked just yet!


I’ve got the same issue with XIBO version 1.8.3 as I’m running segment inside my organization.

Could you please, tell me which file should be modify in my case ?

Thanks in advance.

Whichever docker-compose file you’re using.

So docker-compose.yml if you’re using the standard ports, local MySQL etc.

cms_custom-ports.yml if you’re using custom ports etc

1 Like

Worked like a charm, thank you a lot.

1 Like