Hi, On Fri, Mar 05, Dario Faggioli wrote:
And as "promised", after reboot, /opt is just empty.
Sooo... What's going on? :-)
You did not follow the main mantra: your workload should run in containers or flatpak ;)
Is this a bug or a feature? If it's a feature, it's preventing user to install things like Chrome in MicroOS desktop, so it would be wonderful if we also could think of a workaround. :-O
/opt is for 3rd party software and needs to be writeable, thus is not part of the snapshot. RPM does not have the concept of two databases ... So, if you install an RPM with files in /opt, we have a problem: 1. if we mount /opt for transactional-update, your running services will see the update immeaditly (no longer atomic) and even worse, the software could be broken until the next reboot. 2. if we don't mount /opt for transactional-update, the real /opt will shadow the transactinal-update /opt later, as in your case. The currently only possible solution, and for this the whole system was designed: your workload should run in containers/flatpaks. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)