After docker installation of onlyoffice document-server, mail-server and community server on Ubuntu 22.04, firing up the portal ends up with the portal screen “hanging”:
The running docker images are:
root@ax100:~# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3e469a13ce77 onlyoffice/communityserver "/app/run-community-…" 21 minutes ago Up 12 minutes 0.0.0.0:443->443/tcp, :::443->443/tcp, 3306/tcp, 5280/tcp, 9865-9866/tcp, 9871/tcp, 9882/tcp, 0.0.0.0:5222->5222/tcp, :::5222->5222/tcp, 9888/tcp, 0.0.0.0:90->80/tcp, :::90->80/tcp onlyoffice-community-server 5dab594270c8 onlyoffice/mailserver "/bin/sh -c 'export …" 4 hours ago Up 27 minutes 0.0.0.0:25->25/tcp, :::25->25/tcp, 0.0.0.0:143->143/tcp, :::143->143/tcp, 465/tcp, 993/tcp, 995/tcp, 3306/tcp, 4190/tcp, 0.0.0.0:587->587/tcp, :::587->587/tcp, 8081/tcp onlyoffice-mail-server 2508663b2d57 onlyoffice/documentserver "/app/ds/run-documen…" 4 hours ago Up 33 minutes 80/tcp, 443/tcp onlyoffice-document-server
Note that I had to reroute the community server to port
90:80 in order to avoid port conflict with the
nginx server. Having carefully studied the problem on the internet, the output of the
docker exec -it onlyoffice-community-server systemctl status monoserve command, being
System has not been booted with systemd as init system (PID 1). Can't operate.
worries me as probably being symptomatic of the cause … Your help is much appreciated.