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
  • 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 | Demo | Docs | Install
  1. Cloudron Forum
  2. Feature Requests
  3. enable RW App Containers until restart without debug mode

enable RW App Containers until restart without debug mode

Scheduled Pinned Locked Moved Feature Requests
2 Posts 2 Posters 269 Views 2 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.
    • H Offline
      H Offline
      holm
      wrote on last edited by
      #1

      Hi,

      it would be nice to enable short-lived ReadWrite access for container images, especially for quick and dirty hacks and fixes.

      For example: In the last Synapse update, there was a bug using version x of Pillow where a deprecated attribute (Image.ANTIALIAS) was gone. This made it impossible to upload images to Matrix. Changing a line of code or installing PIL in version y could solve the problem. But not in the ReadOnly container.

      I would like to see a button "Enable RW in container until restart" for non-persistent changes/fixes/debugging/something else.

      A short reminder that all changes are lost on restart would be helpful.

      1 Reply Last reply
      3
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        I like the idea. For lack of a better name, let's call this "lock/unlock" app containers.

        Container starts locked. When unlocked:

        • It will make the container rw
        • Disables automatic updates
        • Gives warning to user that all changes will be lost when updating and are not part of any backups
        • Automatically starts up the container (unlike debug mode which keeps the container in paused mode).

        I think this gives the customer a window to "hotfix" things until upstream (or packaging team) figures out some fix.

        1 Reply Last reply
        3
        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