twinvasup.blogg.se

1. #Install docker collabora code how to#
2. #Install docker collabora code install#
3. #Install docker collabora code update#
4. #Install docker collabora code code#

#Install docker collabora code update#

The way we do this is we mount /var/data/collabora/loolwsd.xml as /etc/loolwsd/loolwsd.xml-new, then allow the container to create its default /etc/loolwsd/loolwsd.xml, copy this default over our /var/data/collabora/loolwsd.xml as /etc/loolwsd/loolwsd.xml-new, and then update the container to use our /var/data/collabora/loolwsd.xml as /etc/loolwsd/loolwsd.xml instead ( confused yet?)Ĭreate an empty /var/data/collabora/loolwsd.xml by running touch /var/data/collabora/loolwsd.xml.

#Install docker collabora code how to#

Until we understand how to pass trusted network parameters to the entrypoint script using environment variables, we have to maintain a manually edited version of loolwsd.xml, and bind-mount it into our collabora container. Upstream collabora-upstream Create loolwsd.xml ¶ We'll need a directory for holding config to bind-mount into our containers, so create /var/data/collabora, and /var/data/config/collabora for holding the docker/swarm config Here's a ( highly technical) diagram to illustrate: It's just a rendering / GUI engine after all, it doesn't hold any persistent data. What if we're running multiple nodes in our swarm, and nginx ends up on a different node to the one running Collabora via docker-compose? Well, either constrain nginx to the same node as Collabora ( example below), or just launch an instance of Collabora on every node then. Now incoming requests to will hit Traefik, be forwarded to nginx ( wherever in the swarm it's running), and then to port 9980 on the same node that nginx is running on. We attach the necessary labels to the Nginx container to instruct Trafeik to setup a front/backend for collabora.

#Install docker collabora code code#

We run a single swarmed Nginx instance, which forwards all requests to an upstream, with the target IP of the docker0 interface, on port 9980 ( the port exposed by the CODE container) We don't want to have to do this manually ( like a cave-man), so we engage in some trickery to allow us to still use our swarmed Traefik to terminate SSL. This presents another problem though - Docker Swarm with Traefik is superb at making all our stacks "just work" with ingress routing and LetsEncyrpt certificates. Using docker-compose will at least provide us with consistent and version-able configuration files. So we have to run Collabora itself in the next best thing to Docker swarm - a docker-compose stack. Preparation ¶ Explanation for complexity ¶ĭue to the clever magic that Collabora does to present a "headless" LibreOffice UI to the browser, the CODE docker container requires system capabilities which cannot be granted under Docker Swarm ( specifically, MKNOD). Docker-compose installed on your node(s) - this is a special case which needs to run outside of Docker Swarm."") you intend to use for LDAP Account Manager, pointed to your keepalived IP Docker swarm cluster with persistent shared storage.CODE is not a standalone app, it's a backend intended to be accessed via "WOPI" from an existing interface ( in our case, NextCloud) It's basically the LibreOffice interface in a web-browser. Add a new nginx server blockĪdd this code to the end of an existing server block or create a new server block for the subdomain you created above.Collabora Online Development Edition (or " CODE"), is the lightweight, or "home" edition of the commercially-supported Collabora Online platform. See How To Issue LetsEncrypt ACMEv2 Wildcard Certs 3. Create subdomain for the Collabora online server $ sudo mkdir /var/2.

#Install docker collabora code install#

This Collabora install is used for integration with Nextcloud.