Persistent Data Across OCI Update

[iprowell]

I'm testing the new OCI feature in PVE 9.1. Overall, it is working well for my use case.

How are people dealing with persistent data? For example, in Homepage, the image I've been testing with, most of the configuration is stored in /app/config, and I would like to have a way to make it persist if I upgrade the OCI image. I've added that as a separate mount point, but there doesn't seem to be an easy way to update the OCI image while maintaining the data in /app/config. I have local ZFS, Linstor ZFS for my cluster shared storage, and a CIFS mount that I use for ISOs, templates, etc.

I guess I could create a new OCI image and then reassign the volume owner where /app/config resides. Is there a better way?

Thanks!

 

[LnxBil]

I guess I could create a new OCI image and then reassign the volume owner where /app/config resides. Is there a better way?

Besides running OCI / Docker Container images in KVM, as it has been for years, no.

Unless the OCI integration is also capable or orchestation, the implementation is a super-niche experimental playground for homelabbers. No enterprise would want to run something like that.

 

[iprowell]

Running and testing a new feature on non-critical services will hopefully improve it. This is a test environment to see how it works. I will lose no sleep if I abandon the attempt in 6 months.