Xibo 1.8.2 on Ubuntu Docker cms web fail to start

Get Help
1

Hello
I setted up Xibo Docker on Ubuntu 16.04 and followed all instructions
but now I face the following problem:
Creating xibo_cms-db_1 …
Creating xibo_cms-xmr_1 …
Creating xibo_cms-db_1
Creating xibo_cms-xmr_1 … done
Creating xibo_cms-web_1 …
Creating xibo_cms-web_1 … error

ERROR: for xibo_cms-web_1 Cannot start service cms-web: driver failed programming external connectivity on endpoint xibo_cms-web_1 (c45e29fde29f9bab9a824f6424c5bcff89801605907bbb754030066a768437ab): Error starting userland proxy: listen tcp 0.0.0.0:80: listen: address already in use

ERROR: for cms-web Cannot start service cms-web: driver failed programming external connectivity on endpoint xibo_cms-web_1 (c45e29fde29f9bab9a824f6424c5bcff89801605907bbb754030066a768437ab): Error starting userland proxy: listen tcp 0.0.0.0:80: listen: address already in use
ERROR: Encountered errors while bringing up the project.

May some one know, the problem with the ports and which setting i have to change?

2

It seems that something else is running on localhost on this port, you’d need to either identify what and remove it if it’s not needed or change the port on which CMS should run.

If you want to change the default port, please see ‘Using different ports’ section of this manual page - http://xibo.org.uk/manual/en/install_docker_linux.html

3

I had the same problem, it turned out to be Apache2 was running on the server outside of the docker modules. Once I stopped that from occurring, the creation of the xibo_cms-web_1 was successful and continued to be successful even after a server reboot.

If I recall correctly, the command is: sudo update-rc.d apache2 disable

That will disable the apache2 daemon from starting, but not remove it completely.

If you need to reenable it at some point in the future, enter: sudo update-rc.d apache2 enable

-Lance

4

That whats exactely the Problem thx Petet and Lance