Restart always with error about loolwsd.xml

[rickywu]

root@syfintech-host002:/data/nextcloud# docker logs thirsty_yalow
Generating RSA private key, 2048 bit long modulus (2 primes)
.....................................+++++
...+++++
e is 65537 (0x010001)
Generating RSA private key, 2048 bit long modulus (2 primes)
.......................................+++++
..........................................+++++
e is 65537 (0x010001)
Signature ok
subject=C = DE, ST = BW, L = Stuttgart, O = Dummy Authority, CN = localhost
Getting CA Private Key
Can't open /etc/loolwsd/loolwsd.xml: Permission denied.
Can't open /etc/loolwsd/loolwsd.xml: Permission denied.
Can't open /etc/loolwsd/loolwsd.xml: Permission denied.
Can't open /etc/loolwsd/loolwsd.xml: Permission denied.
Setting up watches.
Couldn't watch /etc/loolwsd/loolwsd.xml: Permission denied
-rw------- 1 root root 14374 Feb 11 08:20 /etc/loolwsd/loolwsd.xml modified --> restarting
start-libreoffice.sh: line 44:    29 Hangup                  /bin/bash -c "/usr/bin/loolwsd --version --o:sys_template_path=/opt/lool/systemplate --o:child_root_path=/opt/lool/child-roots --o:file_server_root_path=/usr/share/loolwsd ${extra_params}"

Seems not found loolwsd.xml, I just use
docker run -t -d -p 9980:9980 -e "extra_params=--o:ssl.enable=false" collabora/code

docker image id: 3b9a06dbb781 buidld in 3 days ago

[timar]

Did you modify /etc/loolwsd/loolwsd.xml externally? Originally the permission of this file is:
-rw-r----- 1 lool lool 14374 Jan 28 17:58 loolwsd.xml

[rickywu]

@timar No, just pull the image and run it

[rkorn86]

Image changed running UID. I had the same permission problem because of 770d55f. Old uid was 105 and new one is 101. I had to chown manually my external docker volume.

[gohrner]

Commit 770d55f seems to be buggy.
I'm not using external volumes for my CODE container, and running it still fails. UID 101 in the container is assigned to a messagebus user, the lool user is actually 102.

The commit appears to be wrong, or at least incomplete.

[etescartz]

This doesn't work:

$ docker cp romantic_meninsky:/etc/loolwsd/loolwsd.xml loolwsd.xml

As others previously mentioned the file ownership and permissions is transferred to the container and therefore leading to the "Permission denied" error messages

What I did was to cat the heavily edited external file into my Collabora container after starting it as described in the basic setup guide:

$ docker exec -i collabora sh -c 'cat > /etc/loolwsd/loolwsd.xml' < loolwsd.xml

This is creating additional overhead on my deployment routine since I'm using it for my personal Nextcloud instance and I was looking for an automated way to have both Collabora and Nextcloud containers up and running.

Right now this inconvenience looks like it's not worth investing the time to overcome.

HELP:
I would like to use environment variables when launching the Collabora container to achieve the same level of customization but I cannot seem to find that anywhere.

If anyone has a full list of environment variables to use when starting up Collabora containers , please point me towards it.

Getting back to investigating why Collabora still won't work behind my Nginx reverse proxy :(