Suggestion: use squashfs instead of ext2fs
orent opened this issue · 1 comments
Supporting the squasfs image format instead of ext2 would solve two issues at the same time: it would make HTTP transport compression unnecessary as well as help alleviate the hosted image size issue HTTP transport compression is limited to zlib algorithm while squashfs supports zstd or even xz. Enabling modification of existing files would be a little more tricky and would require a per-file COW layer on top.
Layered file systems are tricky to deal with and often cause other trouble. Supporting additional filesystems might be a long term goal of the project, but it is not going to be a priority for us. We'd rather invest effort in providing a performant backend that could also allow hosted persistent storage.