Just tried to upgrade my CODE docker file following https://nextcloud.com/collaboraonline/ - everything went smooth, no errors given. After stopping and deleting the old container I tried to start over - but now CODE won’t work as expected.
Container Logs are like this: https://pastebin.com/XqcrCTYX
Looks like there’s an incomplete filetree installed :-/
I already tried to completely remove and re-install CODE - to no avail.
Anyony else having this problem? Ideas how to solve?
In starter script (/start-libreoffice.sh) there should be collaboraoffice5.3 instead of collaboraoffice5.1. You can modify it, or you can pull a newer image.
I just updated to the latest docker version (2.1, as of May 5h 10:30 CET) and I get that same error. In Nextcloud when I click on a .doc file I get a gray screen.
After logging out and logging in as well as restarting the container as well as restarting docker itself (unfortunately cannot tell which of the above actions - or combination thereof - actually did the trick), the problem went away… to bring a new one: “file not recognized or corrupt” (or something to that effect). I’ve stopped and removed the container and will start again when I have time during the weekend.
I thought with containers things would work more reliably, but there are obviously many things that can go wrong without any clear indication of where the problem is…
I’m also getting the “Failed to fork child processes” with the latest collabora/code docker. I’ve started a new thread at Restarting Docker results in “Failed to fork child processes” - if anybody has any more advice (I’ve tried the “ln -s” method from AlessandroP and had a look at the start-libreoffice.sh script, which seems fine now), I’d be very happy
someone can help us with that error, I’ve been looking for a solution for 5 days and I can not probe everything that lines above but I can not even make the docker work or unpack the content … please help me … I’m willing to pay for the solution.
I have the same issue, with a fresh install of the latest docker image. So the solution above is not useful as it’s already configured with collaboraoffice5.3.