Collabora install in RaspberryPi 3 problem

Hello.

I have installed the Collabora software from Docker, but I have the problem above.

I install Collabora as the nextcloud documentation sais with the command
sudo docker pull collabora/code

After that I put the next command in the CLI
sudo docker run -t -d -p 127.0.0.1:9980:9980 -e ‘domain=collabora\.tiraquelibras\.com’ --restart always --cap-add MKNOD collabora/code

The docker ps shows the proccess working in the 9980 port
pi@raspberrypi:/etc/apache2/ssl $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ebe2c96f768d collabora/code “/bin/sh -c 'bash …” 3 seconds ago Up Less than a second 127.0.0.1:9980->9980/tcp adoring_edison

But this port is not up
pi@raspberrypi:/etc/apache2/ssl $ netstat -an | grep 9980
pi@raspberrypi:/etc/apache2/ssl $

And inmediatly the ps hiddes the port
pi@raspberrypi:/etc/apache2/ssl $ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ebe2c96f768d collabora/code “/bin/sh -c 'bash …” 12 seconds ago Restarting (1) Less than a second ago adoring_edison

The docker log shows these lines:
pi@raspberrypi:/etc/apache2/ssl $ sudo docker logs ebe2c96f768d
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused "exec format error"
standard_init_linux.go:178: exec user process caused “exec format error”

Then, when I try to edit any document it shows that I haven’t permissions??? “Access denied”

And the apache logs shows that:
[Wed Mar 15 18:57:18.133657 2017] [authz_core:error] [pid 21624] [client 212.89.2.250:31639] AH01630: client denied by server configuration: /var/www/nextcloud/data/.ocdata

I haven’t any firewall running:
pi@raspberrypi:/etc/apache2/ssl $ sudo service iptables status
â iptables.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

Anyone know what could happend?

My docker version is:
pi@raspberrypi:/etc/apache2/ssl $ sudo docker version
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 60ccb22
Built: Thu Feb 23 11:32:23 2017
OS/Arch: linux/arm

Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 60ccb22
Built: Thu Feb 23 11:32:23 2017
OS/Arch: linux/arm
Experimental: false

Thank your for your help!!!
Regards

Hello @sbrodriguez
The answer is quite simple and frustrating:
you can’t run the official collabora docker image on a raspberry-pi
The armhf architecture of the raspberry-pi can’t run the x86 instructions compiled in the docker image.
You have several solutions to fix this problem:

  1. The workaround: run the docker image on another x86 computer
  2. The complicated one : (cross-)compile libreoffice Online for armhf architecture on/for raspberrypi

Hello aalaesar.

I have been searching this behavior and the installation with other software (onlyofficce) and everything have the same problem, ARM is not compatible with them.

So, I think that the best solution is change the hardware to another small-servers, like jaguarboard, for example.

Thanks for your answer!!!
Regards

Hello @aalaesar
did you try option 2 yet?

Or is there anyone out there who tried this yet?

Greetings
Michael

Hi Michael. For now i didn’t try crosscompilation for i think a raspberry may not have enough ram to run smoothly a lool service.
Also the resulting compilation take about 11GB of space and need to be optimised a lot before being run on a pi.
But, hey it’s in the pipe! :wink:

1 Like