Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. NocoDB
  3. Cloudron Read-Only File System Breaking Backblaze B2 App

Cloudron Read-Only File System Breaking Backblaze B2 App

Scheduled Pinned Locked Moved NocoDB
4 Posts 3 Posters 1.5k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • 3699n3 Offline
    3699n3 Offline
    3699n
    wrote on last edited by 3699n
    #1

    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.
    erofs read only file system

    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
    
    girishG 1 Reply Last reply
    0
    • 3699n3 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.
      erofs read only file system

      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
      
      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @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.

      fbartelsF 1 Reply Last reply
      1
      • girishG 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.

        fbartelsF Offline
        fbartelsF Offline
        fbartels
        App Dev
        wrote on last edited by
        #3

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

        girishG 1 Reply Last reply
        2
        • fbartelsF fbartels

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

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #4

          @fbartels thanks, I have left a note there.

          1 Reply Last reply
          2

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Bookmarks
          • Search