feat: add support for immutable image#496
feat: add support for immutable image#496thefirstofthe300 wants to merge 1 commit intonextcloud:mainfrom
Conversation
Signed-off-by: Danny Seymour <danny@seymour.family>
865ab65 to
94fb143
Compare
|
Does anything bad happen if those volumes are mounted anyway? It looks like you linked a custom image, which you can absolutely use, but I'm unsure if we support this. Either way, the branch needs to be rebased. @provokateurin are you aware of an immutable mode for nextcloud? I don't really see any issues with merging this, but I also don't have a quick way to test it. |
|
Nextcloud is not really immutable. It will probably run into quite a few issues because all code assumes the whole dir is writable. |
|
@provokateurin sorry for necroposting, but I couldn't find an answer searching in here or the the docker/server repos - is there any effort being made to change that? Running with the entire codebase in shared writable persistent storage makes for a pretty bad experience; those types of storage tend to be (necessarily, for consistency across networks) quite slow. There's no reason that config files can't live in mutable storage, but I wouldn't think the PHP code would need to overwrite itself (or HTML/JS/CSS, for that matter) |
|
Sorry I'm not involved in the Helm Chart anymore, however the read-only aspect is a matter of packaging (docker image) and configuration. For example NixOS (which is what I use nowadays) has the entire source code read-only in the nix store, so it is absolutely possible. |
|
I'll raise an issue there. Thanks for the info! |
Pull Request
Description of the change
Nextcloud is capable of being built using an immutable image (see https://github.com/thefirstofthe300/nextcloud-docker). In this scenario, there is no point in mounting the
/var/wwwand/var/www/htmldirectories to store state. The remaining directories should be mounted, but not these two.Benefits
Allows users to build their own immutable images which do not perform an rsync on start but still use this chart.
Possible drawbacks
The default values are not changing so I see no drawbacks.
Additional information
Chart.yamlaccording to semver.