How to enable automatic reboot on ucore when updates are staged?

uCore
1

From the uCore readme, talking about differences from CoreOS:

  • Disables Zincati auto upgrade/reboot service
  • Enables staging of automatic system updates via rpm-ostreed

For those using uCore on bare metal, what solution do you have to have automatic reboot when updates are staged?

I’m sure it can be done with a little systemd unit to check “bootc status” then reboot if needed.. If I can just copy that from someone that would be awesome!

Or better yet, could we contribute that to uCore itself? Perhaps disabled by default but easy to enable for folks who want it?

2

I was wondering the same thing. I haven’t yet installed uCore though.

Or better yet, could we contribute that to uCore itself? Perhaps disabled by default but easy to enable for folks who want it?

The project’s lead is thinking about retiring uCore, so I’m not sure it would be worth it. And the README on the Github repo does say that there are upstream efforts to develop an alternative.

However, as I wrote in the other thread, I think @bsherman’s suggestion to use CentOS bootc image as base is the right idea. I find the whole butane/ignition thing to be a bit too outside the usual container practices. I think I’m going to base by home server on CentOS bootc instead.

And yes, I’d consider a systemd unit. I’ve been running wild with systemd user units since @CerealParadox shared his config snippet for his starship prompt. :grin: (I made one for brew updates and one for dnf updates for my Fedora WSL at work.)

Tip: there’s a VS Code extension for Systemd unit files:

1 Like
3

There’s actually an open issue to address the Zincati question. At the time uCore was created, Zincati did not work on container-native installs like ours. Since then it seems Zincati has been fixed to work!

We just need to test it and decide how to transition back to using it. But certainly we need to update the README with correct information.

1 Like