Closed stellarpower closed 6 months ago
i'm facing the same problem.. any progress?
So far things seem to be stable having pulled a new image since opening the issue, although we aren;t sure for definite this hasn't come up at some point since then.
Can you please retest this and comment, also see if related to #2800.
No response, I close.
Describe the bug A clear and concise description of what the bug is.
To Reproduce
Description
We are in a rootless container under podman, behind a reverse proxy (so TLS not required and set to termination), pretty much the default compose setup as given in the online docs.
I have been launching privileged whilst trying to work this out, ideally would then cut back permissions later.
We were getting a whole load of messages about failure to bind mount, so have set mount_jail_tree to false in the configs to quieten these and redeployed.
However, after some time, the active document is "unable to connect to the server" and nextcloud bails out from that page:
(full logs available below).
I've seen several messages with it still trying to mount /dev/random into one of the jails, and we get a message saying that the systemplate is mounted read-only (don't know why, it's not a volume), and that it's failing to walk the filesystem tree in linkOrCopy(
nftw()
failed).At this point, nextcloud still complains that it can't connect to the server upon closing the previous page and opening a different document.
Restarting the container may have helped sporadically, the first time we restarted we then got a segfault in the OConfigurationTreeRoot ctor from coolforkit's globalPreinit - this is included in the full logs below, and I presume the segfault is due ot a messup in the container root-caused by the above.
I also concerningly noted in early startup that collabora was trying to remove and replace coolwsd.xml, which it then failed to do as this was bound in as a config.
It seems to me that the image is requiring permissions that are typically not available in a rootless setup - either by default or by necessity (e.g. making device nodes should not be possible on the host unless running as root, so there is no way to achieve this in side the container). If there isn't a reasonably straightforward fix to this issue, I guess potentially the way the jails are architected may need to be reconsidered if launching without a rootful container setup.
Thanks!
Logs
coolwsd.xml
As the example from the repository, but with mount_jail_tree set to false. link
Compose file:
Another attempt - container removed and replaced:
Desktop (please complete the following information)