Cloudron Read-Only File System Breaking Backblaze B2 App

[3699n]

When trying to enable the Backblaze B2 app in NocoDB, a cloudron-specific error is occuring where the testing of the configuration fails due to the read-only file system of cloudron apps. This prevents the B2 app from functioning properly. I have confirmed with a NocoDB developer that this issue is Cloudron specific.

Nov 10 04:44:50 p :: [Error: EROFS: read-only file system, open '/app/code/temp.txt'] {
Nov 10 04:44:50 errno: -30,
Nov 10 04:44:50 code: 'EROFS',
Nov 10 04:44:50 syscall: 'open',
Nov 10 04:44:50 path: '/app/code/temp.txt'
Nov 10 04:44:50 }
Nov 10 04:44:50 POST /api/v1/db/meta/plugins/test 400 65 - 32.846 ms
Nov 10 04:45:00 GET /dashboard 301 185 - 4.418 ms

[girish]

@3699n said in Cloudron Read-Only File System Breaking Backblaze B2 App:

Nov 10 04:44:50 p :: [Error: EROFS: read-only file system, open '/app/code/temp.txt'] {

The app is trying to write to the code directory. Do you know why? Why is it creating temp files in code directory and not under /tmp/ ?

If you think about it, Cloudron is doing the right thing, it's why the read only setup exists. We don't want apps to modify/write the code and create security issues. If they create "data" inside code directories, then how is one supposed to create a proper backup or upgrade ?

@3699n If you are in touch with the upstream author / have a github issue, I am happy to follow up.

[fbartels]

@girish this is the one it seems https://github.com/nocodb/nocodb/issues/4213

[girish]

@fbartels thanks, I have left a note there.