Investigate potential issue if cloning in a read-only folder/file system

[leafty]

Logs from the legacy python git-clone:

File "/usr/local/lib/python3.11/pathlib.py", line 1116, in mkdir
os.mkdir(self, mode)
PermissionError: [Errno 13] Permission denied

Check if the go version would also fail.

[sgaist]

The shellclone go replacement currently used in the cloner image also fails with a permission denied.
It is an implementation that follows the same logic as the legacy python version and should error in similar fashion although the message might differ a bit.
In this case:

2026/07/23 08:32:16 failed to create clone path:mkdir /tmp/renku/renku: permission denied

[leafty]

Maybe we can try to make the cloner process not fail (no repositories cloned). This way the renku session would start (with no repositories). This is a low priority item thoug.

[sgaist]

So all possible errors happening during the preparation up to cloning should go into a file and the process go as far as possible ?

[leafty]

So all possible errors happening during the preparation up to cloning should go into a file and the process go as far as possible ?

If it's not possible to create the folders for each repository, then I'm not sure how we could create a file? In this case, we should print in the logs that cloning has failed because the RENKU_MOUNT_DIR is not writeable.

[sgaist]

Sorry, what I meant was: outside of this specific issue where there's not much the cloner can do beside printing, should we log other errors in a file at the root of RENKU_MOUNT_DIR in a similar fashion we do for cloning errors within the clone path ?

That way if there is something strange happening outside of a literal clone problem, the user can see it right away rather than wonder what happened. Checking the logs of an init container might not be what comes first to mind.