nextcloud / richdocuments

📑 Collabora Online for Nextcloud
https://nextcloud.com/collaboraonline
352 stars 116 forks source link

App nextcloud office doesn't work on docker image nextcloud:stable-fpm-alpine #2602

Closed leomeinel closed 1 year ago

leomeinel commented 1 year ago

Describe the bug When trying to open existing or creating new documents I get an infinite loading screen. I am using docker. The images are:

This setup works pretty well so far, the only real issue I have is with the Nextcloud Office app and the built-in CODE server.

To Reproduce Steps to reproduce the behavior:

  1. Install my setup as mentioned above
  2. Install apps: "Collabora Online - Built-in CODE Server" and "Nextcloud Office"
  3. See in .../settings/admin/richdocuments that "Collabora Online server is reachable."
  4. Try to load or create document
  5. See an infinite loading screen

Expected behavior Nextcloud office loading the document and office suite.

Client details:

Server details

Operating system: Fedora Linux 36

Web server: nginx:stable-alpine (Docker) 1.22.1

Database: yobasystems/alpine-mariadb (Docker) 10.6.10

PHP version: 8.0.25

Nextcloud version: nextcloud:stable-fpm-alpine (Docker) 24.0.7.1

Version of the richdocuments app: 6.3.1

Version of Collabora Online: 22.5.702

Logs #### Nextcloud log (data/nextcloud.log) ``` not relevant ``` #### Browser log ``` not relevant ``` #### Webserver log ``` 2022/11/06 22:57:43 [error] 24#24: *97 FastCGI sent in stderr: "PHP message: richdocumentscode (proxy.php) error exit, PID: 24, Message: no_glibc" while reading upstream, client: 10.2.0.x, server: foo, request: "POST /custom_apps/richdocumentscode/proxy.php?req=/lool/convert-to/png HTTP/1.1", upstream: "fastcgi://10.2.0.y:bar", host: "foo" 2022/11/06 22:57:43 [error] 24#24: *101 FastCGI sent in stderr: "PHP message: richdocumentscode (proxy.php) error exit, PID: 21, Message: no_glibc" while reading upstream, client: 10.2.0.x, server: foo, request: "POST /custom_apps/richdocumentscode/proxy.php?req=/lool/convert-to/png HTTP/1.1", upstream: "fastcgi://10.2.0.y:bar", host: "foo" ```

My conclusion: Either Nextcloud office or CODE require glibc which is not supported by nextcloud:stable-fpm-alpine. I don't know if this is known/intended but I wanted to make you at least aware and would kind of want to ask for a fix.

Fixing it should be possible by not having either of those binaries linked to glibc!

leomeinel commented 1 year ago

This seems to be related. AppImages might be the problem here. This is the issue for AppImage

leomeinel commented 1 year ago

I will leave this open for now, feel free to close it if you think that it is not relevant to your software because of the linked issues. However I'm not sure if this is actually the cause of the issue.

leomeinel commented 1 year ago

A solution might also be setting up CODE in another docker container

joshtrichards commented 12 months ago

The Collabora Online - Built-in CODE Server is a separate app. This app (here) works both with the Built-in edition as well as in the independent - i.e. own Docker container - edition. The repository relevant to your Issue is this one:

https://github.com/CollaboraOnline/richdocumentscode

And its system requirements state it requires glibc (alpine is musl based):

https://github.com/CollaboraOnline/richdocumentscode#system-requirements

If you want to advocate for an enhancement, check/open an issue here: https://github.com/CollaboraOnline/richdocumentscode

leomeinel commented 12 months ago

The Collabora Online - Built-in CODE Server is a separate app. This app (here) works both with the Built-in edition as well as in the independent - i.e. own Docker container - edition. The repository relevant to your Issue is this one:

https://github.com/CollaboraOnline/richdocumentscode

And its system requirements state it requires glibc (alpine is musl based):

https://github.com/CollaboraOnline/richdocumentscode#system-requirements

If you want to advocate for an enhancement, check/open an issue here: https://github.com/CollaboraOnline/richdocumentscode

Thank you very much for clarifying. I should have specified, why I have closed this issue because I already figured out that this is the wrong place to ask and then just gave up on the issue. If I find the time (I will probably not) I might report this in the right place with more details.