On Wed, Mar 1, 2023 at 9:05 AM Robert Schweikert <rjsch...@suse.com> wrote: > > Hi, > > At present cloud-init stores data in /var/lib/cloud. For systems with > transactional-updates, i.e. opensuse-microos and other incarnations this > location becomes read-only. > > Would it be OK to send a PR that moves the data to /var/cache/cloud ? > > I'd prefer a wholesale move of the data over various if conditions and > checks whether or not /var/lib is writable. Also we'd know that as of > version X of cloud-init the data has been moved. > > Basic idea is > > if no os.exists('/var/cache/cloud'): > create_it > if os.exists('/var/lib/cloud'): > move_the_existing_data_to_new_location > > Do the above early enough in the process such that for all other > locations in the code that access the data the change in location is > transparent. > > Thoughts?
That doesn't make any sense. openSUSE systems are explicitly supposed to omit /var from the read-only root. That's why the RPM and DNF databases were moved to /usr years ago. The whole point of /var is for system specific data. It is supposed to be always writable. -- 真実はいつも一つ!/ Always, there's only one truth! -- Mailing list: https://launchpad.net/~cloud-init Post to : cloud-init@lists.launchpad.net Unsubscribe : https://launchpad.net/~cloud-init More help : https://help.launchpad.net/ListHelp