Nextcloud with Collabora/Docker on Gentoo

[NismoC32]

Hi
I'm trying to get collabora to work on my Gentoo server, but have run in to some problems I haven been able to solve.

Se the details in this thread on Nextcloud:
https://help.nextcloud.com/t/problem-getting-collabora-to-work-in-gentoo-with-docker/23259

Let me know if more info is needed.
Maybe someone here can help figure out whats wrong.

PS: Havent gotten apache access_log to work ether.

Thanks.

[NismoC32]

It looks like connection to https://127.0.0.1 is refused when attempting to connect to 127.0.0.1:9980
When I run 'docker ps' I get the following list:

[msst]

I have a nextcloud installation here as well. All working fine.

Was also once interested to install collabora. Then I saw it is only available as a docker crap version and have nor pursued it. Should anyone find out how to completely de-docker that stuff without a huge hassle and install it normally I may give it a try.

And by the way: If the docker stuff gives config troubles a normal installation likely bypasses that, because a normal installation should allow you to run it of your normal apache:80 system.

[Elleni]

I am in the same boat, have a nice nextcloud installation here, and did not install colabora online cause of docker version. Then I have seen onlyoffice which offers similar functionality, and there is even an ebuild that compiled fine:
https://gpo.zugaina.org/app-office/onlyoffice
But I found no explanation where to go from there. If anyone is able to get it working, I would be glad to get any hint

[NismoC32]

I do agree with you guys.

The only reason for trying to get docker/collabora to work is that it would be a nice tool for
me know when I'm studying in another country.

Maybe I should look into onlyoffice instead.

[Elleni]

if you do and find out what to do after compiling onlyoffice, please share

[NismoC32]

Hmm I might be wrong here but the 'ebuild' in the link over is for the desktop version of the suite
and not what they call the integration edition that is needed for integration with cloud servers.

If you look at this link on the onlyoffcie's web page regarding nextcloud it looks like you have to pay
to get the integration edition.
Check this link: https://www.onlyoffice.com/connectors-nextcloud.aspx
You at lest get a 30 day trial time.

One more thing, it seems to only support MS office formats, so this is at least a deal breaker for me.

[szatox]

NismoC32, I had to install nc + collabora recently, it took a bit of digging on the internet, trying and failing, but I eventually got it ot work using those 2 guides:
https://docs.nextcloud.com/server/12/admin_manual/installation/source_installation.html
https://www.linuxbabe.com/cloud-storage/integrate-collabora-online-server-nextcloud-ubuntu-16-04
Those guides are for ubuntu, but it's irrelevant since they regard manual process.

Now, I tihnk I set it with 2 separate domains (so vhost 'nextcloud' served nextcloud instance and vhost 'collabora' was set with all the proxy stuff you can find in that guide - take this bit with a grain of salt though, it's been some time ago)
However, the most critical part was this one: at some point you will be asked for collabora's domain. Your answer (the parameter provided to docker as -e 'domain=<your answer>) is "nextcloud\\.your\\.domain"
Yup. You're expected to enter the domain assigned to nextcloud instance rather than collabora. And you escape dots with double backslashes.

[NismoC32]

Thanks for the info szatox.

I have now concluded that my problem is docker.

Here is my problem, when I start the image with
docker run -t -d -p 127.0.0.1:9980:9980 -e 'domain=mydomain\\.com' --restart always --cap-add MKNOD collabora/code

My nextcloud url is https://mydomin.com
My collabora url is https://office.mydomain.com

The docker ps shows:

[szatox]

I'm not a big fan of docker and I don't know its design, but setting storage driver to device mapper seemed important. You have it set to btrfs. I had similar issues there and I suppose this was the cause.
Also, I think it's supposed to work with routed networking (AKA NAT mode) rather than with bridged networking, though I'm not quite sure how to read this output from your docker info. Either way, set storage driver first.

[NismoC32]

Well I have now changed the btrfs storage driver to overlay2 on a ext4 file system and that fixed the problems with
docker. It now works like it should Thanks szatox.

Here is the output from 'ip addr' after docker now working.:

[szatox]

Good, at least one thing sorted out.
Now, as I said before I'm not a big fan of docker and I had rather a limited experience with it. Either way, collabora actually exposes a port and a socket, so perhaps you're already set with this part. Maybe some other members could chime in on the topic of docker's networking.

Anyway, where are you with the proxy part? Do you have your vhosts ready? Are apache's proxy modules enabled? AFAIR you need proxy, http proxy and wss proxy or something like that.
Can you poke at that vhost with curl and see any valid response? (and http 503 bad gateway when collabora is down?)
Any problems / errors there?

The final step is about enabling collabora (And providing collabora's address: office.something.... I suppose 127.0.0.1 would also work if you bound the proxy vhost to our loopback, making second domain expendable. Haven't tested.) in nextcloud administrator's panel.