online
online copied to clipboard
Collabora - Nextcloud: sh: 1: /usr/bin/coolmount: Operation not permitted
Describe the Bug
When closing a document, coolmount gives the following error in the docker container.
Steps to Reproduce
In Nextcloud open a document, in my case a docx.
Close the document.
Observe the errors:
[ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:524
and
sh: 1: /usr/bin/coolmount: Operation not permitted
Expected Behavior
No errors when using the application for its purpose.
Actual Behavior
Errors appear which do not give much trust in the application working correctly. Document editing works fine though.
Screenshots
` Client: Docker Engine - Community Version: 26.1.0 API version: 1.45 Go version: go1.21.9 Git commit: 9714adc Built: Mon Apr 22 17:06:56 2024 OS/Arch: linux/amd64 Context: default
Server: Docker Engine - Community
Engine:
Version: 26.1.0
API version: 1.45 (minimum version 1.24)
Go version: go1.21.9
Git commit: c8af8eb
Built: Mon Apr 22 17:06:56 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.31
GitCommit: e377cd56a71523140ca6ae87e30244719194a521
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0
`
I'm having the same error with coolwsd=24.04.5.1-1 in a debian bookworm LXC container, though it may not be related to the Collabora version.
Initially I was investigating some error logs like
/usr/bin/coolmount: forced unmount of [/opt/cool/child-roots/244786-cf3802a9/tuNzza9XMJ1KraCf/lo] failed: Permission denied.
which were not preventing from properly using the product. I then saw this similar issue https://github.com/CollaboraOnline/online/issues/5164 and tried the user-suggested fix here. I'm no longer having the errors I was having, but they are now replaced by
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
in the journal. Same as the bug report, I can properly edit/save/export documents, so I'm not sure what's malfunctioning here if anything :)
This issue is still persistent in version 24.x
Had a similar issue, and the document would not load on nextcloud…
I fixed it by adding the --privileged option to the container (it was optional on debian until now if I remember correctly, but a colabora, debian or docker update may have changed this?)
Had a similar issue, and the document would not load on nextcloud… I fixed it by adding the
--privilegedoption to the container (it was optional on debian until now if I remember correctly, but a colabora, debian or docker update may have changed this?)
The weird part is that my instance DOES load the document fine, but the error is still concerning.
We encounter the same problem.
We can actually ignore the error message and just leave it where it is and work in the background, but I guess there should be a fix for this, right?
We encounter the same problem.
We can actually ignore the error message and just leave it where it is and work in the background, but I guess there should be a fix for this, right?
It should be fixed yeah, in my opinion.
Any updates on this?
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
frk-00028-00028 2024-10-18 11:19:50.484548 +0200 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
frk-00028-00028 2024-10-18 11:19:50.912144 +0200 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585
frk-00028-00028 2024-10-18 11:19:50.920355 +0200 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585
frk-00028-00028 2024-10-18 11:19:51.221057 +0200 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
frk-00028-00028 2024-10-18 11:19:51.488682 +0200 [ forkit ] WRN The systemplate directory [/opt/cool/systemplate] is read-only, and at least [/opt/cool/systemplate//etc/hosts] is out-of-date. Will have to copy sysTemplate to jails. To restore optimal performance, make sure the files in [/opt/cool/systemplate/etc] are up-to-date.| common/JailUtil.cpp:585
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
sh: 1: /usr/bin/coolmount: Operation not permitted
这个问题有被解决吗? 我部署在k8s中也有相同的问题
Translation: Has this issue ever been resolved? I have the same problem deploying in k8s
这个问题有被解决吗? 我部署在k8s中也有相同的问题
As far as I know, it is not.
That is not an error but a warning, so no bug but expected behavior and nothing to fix here.