enable RW App Containers until restart without debug mode
-
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.
-
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.