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

**URL:** <https://universal-blue.discourse.group/t/how-to-enable-automatic-reboot-on-ucore-when-updates-are-staged/8948>\
**Category:** uCore\
**Created:** [June 4, 2025, 6:08pm UTC](https://universal-blue.discourse.group/t/how-to-enable-automatic-reboot-on-ucore-when-updates-are-staged/8948 "2025-06-04T18:08:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pauldoo](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/pauldoo/32/892_2.png) [@pauldoo](https://universal-blue.discourse.group/u/pauldoo)\
**Post date:** [June 4, 2025, 6:08pm UTC](https://universal-blue.discourse.group/t/how-to-enable-automatic-reboot-on-ucore-when-updates-are-staged/8948/1 "2025-06-04T18:08:16Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![SylChamber](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/sylchamber/32/6422_2.png) [@SylChamber](https://universal-blue.discourse.group/u/SylChamber)\
**Post date:** [June 6, 2025, 12:57am UTC](https://universal-blue.discourse.group/t/how-to-enable-automatic-reboot-on-ucore-when-updates-are-staged/8948/2 "2025-06-06T00:57:21Z")

</div>

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](https://universal-blue.discourse.group/t/ucore-retirement/8975/4), 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](https://universal-blue.discourse.group/t/updates-thread/8833/13). 😁 (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:

> **[Systemd Helper - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=hangxingliu.vscode-systemd-support)**
>
> Extension for Visual Studio Code - A Visual Studio Code extension that helps you read and write Systemd unit/mkosi config/Podman Quadlet files

---

<div class="post-metadata">

**Author:** ![bsherman](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/bsherman/32/112_2.png) [@bsherman](https://universal-blue.discourse.group/u/bsherman)\
**Post date:** [June 13, 2025, 12:38am UTC](https://universal-blue.discourse.group/t/how-to-enable-automatic-reboot-on-ucore-when-updates-are-staged/8948/3 "2025-06-13T00:38:59Z")

</div>

> [@pauldoo](#):
>
> 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?

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.

> <https://github.com/ublue-os/ucore/issues/54>
>
> We currently disable zincati by default and have a note in README about it not w…orking with ostree containers.
> 
> When this is fixed we should revisit use of zincati rather than rpm-ostreed-automatic.timer
> 
> https://github.com/coreos/fedora-coreos-tracker/issues/1263