HowTo: Install Collabora Online on Ubuntu 16.04. (without Docker!)


#21

@Sanook I already thouht that a self compiled version runs faster than the docker container. But is it really worth it? So how big is the gain?
For self-compiling you’ll need a lot more disk space (just the dependencies for LO are as big as the docker image) and I think that it is harder to maintain.


#22

I presume the biggest gain is it comes without the throttling and 10 user limit that the docker container enforces.


#23

I don’t know of any docker containers that are built for ARM hardware. I’m attempting to build a raspberry pi server using these instructions now due to this issue. So you would build this from scratch if either the hardware the docker container is built on is not supported, or if you need to customize it significantly in any way. I’m attempting to run this on a dedicated raspberry pi server. So my raspberry pi is my “container” in my case. I searched, and this was the best solution I have found so far to run this type of server on a Raspberry Pi. If anybody has any more information about that, I’m sure I wouldn’t be the only person interested.

I was completely unaware of any “throttling” in the docker container. Is this true? Why would there be any “throttling” and a 10 user limit?


#24

Yeah a Arm collabora container would be brilliant.

I can not give you definites as its all a little hazy from Collabora, but by users.

I found this which is actually the reverse of what we need.


But it is the reverse and so do we only need qemu-x86-static and the reverse is true?

The Resin.io forums have a lot of community info on raspbian containers.
https://forums.resin.io/c/projects

https://hub.docker.com/r/ioft/armhf-ubuntu/

https://hub.docker.com/r/forumi0721alpinearmhf/alpine-armhf-nginx/


#25

PS slightly tangential but something that might be of interest to the RPi community.

https://arnoldthebat.co.uk/wordpress/2016/12/18/chromiumos-builds-for-rpi/


#26

Are you trying to get somebody to build a dockers image? I don’t see why you posted all that stuff otherwise. The post about chromium is off topic.


#27

You asked a question and I answered.

“I was completely unaware of any “throttling” in the docker container. Is this true? Why would there be any “throttling” and a 10 user limit?”

On x86 Arm containers can be provided by using qemu.
On ArmHf if that its true then can the reverse not be done by the same.

Yes Arm containers do exist and there are some.

Yes it was off topic and I did say so but might be of interest to RPi fans.

I am interested in ArmHf and currently the removal of the Document app and a Docker container will not run on Arm is a huge stopper.

Yes I would like Collabora to build an ArmHf container or maybe it might be possible to run the x86 one through Qemu emulation.


#28

OK. I meant Docker containers with Collabora built in them. I know that docker is running very well on the pi. I’ve built some myself.


#29

I am looking at some of the newer 64bit TV-boxes and I completely agree with you, as its not just RPi, phones, TV boxes, SBC and Arm is making roads into data centers.
Doesn’t make sense for Collabora, not to provide a container for Arm hosts.

Yeah I just posted a few Arm host containers as they are a bit thin on the ground.


#30

Hey guys,

I tried to install Collabora with this Tutorial but i stuck at step 2. loolwsd is missing. I read the comments and found out that there are files in wsd. I moved them from that directory. But when I try make I get the error " loolwsd ‘configure.ac’ is required".

Any hints how I can solve this?

Kind regards


#31

Like @Christopher_Swain and @NextTyrael I’m experiencing the following and therefore can’t compile wsd/loolwsd:

@Pisoko or someone else: can you give as a hint what to do?


[HOWTO] Collabora 2.0 without using Docker not for prod
#32

I was attempting to compile this on a Raspberry Pi that I am testing, but it is taking forever. I see in the GIT repository that that directory is gone. It looks like they might have changed the name from loolwsd to just wsd? So just replace all the references in the instructions from loolwsd to wsd? I can’t seem to test it at the moment.


#33

@twentyninehairs Yes they’ve changed the directory name. But thats not the problem. Aclocal can’t find the file configure.ac. As you can see in the git there is no such file. Therefore the build process can’t be proceeded at the moment.


#34

I have had that prob before and you run out of memory you need to start the pi without a desktop and then run.
In fact compiling anything, do it without the desktop as with 1gb it is short of memory, when it gets low it grabs back caches and buffers and becomes a complete dog.


#35

Oh, right. Sorry, missed that detail. So maybe that is a dynamically generated file during the make? Did part of the make crash, and not create that file?


#36

Is it possible to install Collabora without root access?


#37

@Hanzei The short answer to your question is no. :slight_smile: That is, if you don’t already know, then definitely not. I suppose if your server already happened to have all the prerequisites in place, maybe, but that’s almost definitely a no.


#38

I was attempting to build this on a Raspberry Pi 1 B (512mb RAM) as just a test before buying a Pi 3 to run a real server from. After several off and on attempts, I found that first GIT clone was causing my Pi to run out of memory and start swapping. (I have a swap partition.) I didn’t really know what was going on until I really sat down and dug into it. It was swapping throughout the process, and would crash halfway through. Maybe I should just download the files to another computer, then transfer them to the Pi, I suppose. I did build a more robust swap system on a flash drive; we’ll see if that works first. This is taking a long time though for a test that might not work, though.

I’m running DietPi for the stripped OS, and I don’t install any UI stuff. DietPi is amazing software for the Pi, by the way. The developer did a really good job.


#40

You must do a little thing before make this command to work :
sudo apt-get build-dep libreoffice -y

You have to edit /etc/apt/sources.list and uncomment some deb-src lines then make a apt update and lunch apt-get build-dep libreoffice -y


#41

hey guys, am trying to install collabora without docker but stuck trying to compile libreoffice, keep getting the error below.
I installed all the dependencies

make[5]: Entering directory '/apps/libreoffice/core/workdir/UnpackedTarball/firebird/gen' rm -f metadata.fdb /apps/libreoffice/core/workdir/UnpackedTarball/firebird/gen/Release/firebird/bin/isql -q -i /apps/libreoffice/core/workdir/UnpackedTarball/firebird/src/dbs/metadata.sql can't format message 17:0 -- message file /apps/libreoffice/core/workdir/UnpackedTarball/firebird/gen/Release/firebird/firebird.msg not found Your user name and password are not defined. Ask your database administrator to set up a Firebird login. can't format message 17:120 -- message file /apps/libreoffice/core/workdir/UnpackedTarball/firebird/gen/Release/firebird/firebird.msg not found Makefile:325: recipe for target 'metadata.fdb' failed make[5]: *** [metadata.fdb] Error 1 make[5]: Leaving directory '/apps/libreoffice/core/workdir/UnpackedTarball/firebird/gen' Makefile:166: recipe for target 'master_process' failed make[4]: *** [master_process] Error 2 make[4]: Leaving directory '/apps/libreoffice/core/workdir/UnpackedTarball/firebird/gen' Makefile:66: recipe for target 'firebird' failed make[3]: *** [firebird] Error 2 make[3]: Leaving directory '/apps/libreoffice/core/workdir/UnpackedTarball/firebird/gen' Makefile:6: recipe for target 'firebird' failed make[2]: *** [firebird] Error 2 make[2]: Leaving directory '/apps/libreoffice/core/workdir/UnpackedTarball/firebird' /apps/libreoffice/core/external/firebird/ExternalProject_firebird.mk:37: recipe for target '/apps/libreoffice/core/workdir/ExternalProject/firebird/build' failed make[1]: *** [/apps/libreoffice/core/workdir/ExternalProject/firebird/build] Error 1 make[1]: *** Waiting for unfinished jobs.... Makefile:256: recipe for target 'build' failed make: *** [build] Error 2