I just tested this, but it doesnāt change the delayā¦ Is CODE using the /opt/lool/systemplate/etc/resolv.conf file?
no - this is the problem. docker ensures that the /etc/resolv.conf is provided via a special mount (so the contents of this file inside the image are not actually used). the --dns-ip option allows you to override the default action which is to simply use the contents of the host /etc/resolv.conf. normally this option isnāt required unless you have a nameserver bound to the loopback adapter of the host or similar weird/special config.
from what I understand the /opt/lool/systemplate/ is like a chroot jail used by the environment of the document editor, so itās the collabora subprocess which sees this as the resolv.conf to use. this comes factory prepared from the person who packaged this image as 192.168.100.1 (and it was 192.168.65.1 in the previous release).
@guddl 's response above seems like a good solution to this issue - assuming that the chroot jail or whatever collabora uses is happy with a symbolic link.
iām guessing that since the /etc/resolv.conf is mounted in by docker that it would probably be recommended to rename the file and create the symbolic link in the /start-libreoffice.sh or /etc/rc.local or something simiilar. iām not sure how solid a symbolic link to a mount would be.
ok. iāve got this working ok now. i removed the /opt/look/systemplate/etc/resolv.conf file and modified the beginning of /start-libreoffice.sh so it reads like:
#!/bin/sh
# Fix lool resolv.conf problem (wizdude)
ln -s /etc/resolv.conf /opt/lool/systemplate/etc/resolv.conf
# Generate new SSL certificate instead of using the default
iāve run some tcpdumpās and Iām not seeing any DNS query related problems anymore. Collabora Online is working great - nice and quick and no more delays.
i think the creator of this docker should be notified of this issue. are they here reading this thread? or do I need to report this back somewhere else?
@jospoortvliet can you point this issue and the solution to the team which created the docker container? Maybe it would be good to explain a bit more how the docker container is created, or share the Dockerfile, so more people can have a look at it/improve it? Thanks!
thank you for your solution but it does not rule my house.
I have the resolv.conf I delete and I do well the symbolic link.
by cons must restart after you?
For information on symbolic link is removed if I stop the docker, you must then redo the symbolic link.
ps: I have two for a certificate for a nextcloud and collaborated.
You have an idea?
If I understand you correctly, you mean you canāt find a way to open the Collabore office suite from inside Nextcloud?
For this you have to install an app: youāll need to enable experimental apps (not sure about this however) and then go to the Productivy section and enable the āCollabora Onlineā app.
This is thread is becoming flooded and useless because of our off-top, admin panel is not related to connecting delay and itās not part of Nextcloud, itās part of LibreOffice Online.
I donāt use docker and not sure how admin panel works there, but if you use LibreOffice Online without docker then the address is as follows:
for those who are interested, iāve lodged bug report 101809 with the libreoffice people so that someone can attend to the issue with the docker image.
I pushed a new collabora/code docker image to docker hub, which has a fix for the āspecial characterā problem. The docker image did not have the locales in it, and lacale set to POSIX. However, in this case LibreOffice can handle only ASCII file names. The solution was to install all locales, and I set en_US.UTF-8 in the environment. Thanks for the bug report.
Is there any chance to have ARM (aarch64) docker images? I guess many of us have those SoC as own/nextcloud server and it would be great to play with CODE.
