micro OS

[malcolmlewis]

@Neal

The underlying OS does need to be rebooted if a update requires it …otherwise it would not be applied. I assume on reboot it merges the changes into the immutable filesystem then marks it immutable again. Have you ever tried to run manually “transactional-update”? If there’s a update that requires reboot it tells you that you must reboot the OS or data might be compromised. I manually did this last night after a fresh install and it told me to reboot. Or install a package “transactional-update pkg install nano” …it has me reboot or otherwise nano isn’t installed. FYI…I found this which says you can control the updates on your schedule. As far as the containers podman or docker should update and that’s outside of the OS and I can control that as well.

Kubic:Update and Reboot - openSUSE Wiki

Hi
But again, if I need a package, that would be installed at setup via the vagrant file and a reload on completion (or as indicated AutoYaST for bare-metal).

For a single bare-metal node, you will always be updating/rebooting I don’t see any other way around that.

I think you need to look at adding some hardware, or maybe upgrade the CPU in the NUC?

Oh, if you do play with Rancher-Desktop, check out the dashboard…