https://blue-build.org/ logo
Powered by
Auto updates
# questions
m
Hey, it's my understanding that ublue images come with auto updating configured out of the box. I can see that my GH actions have successfully gone off, there is a new 
latest
image, but I haven't gotten any updates pending. 
rpm-ostree status
does show that the automatic update timer was last run 11m ago.
Copy code
automaticUpdates: stage; rpm-ostreed-automatic.timer: last run 11min ago
My recipie https://github.com/matt-savvy/bluebuild/blob/main/recipes/recipe.yml Am I just looking in the wrong place? Thanks
a
message has been deleted
g
Updates only get applied after you reboot. Did you do that?
m
Yup, I've rebooted
Is there somewhere I would be able to see any updates that are "on deck" to be applied at the next reboot?
I've used 
bluebuild switch
, could that be part of it?
I've just gone ahead and updated with the current latest in my registry with 
bootc switch
, I'll check in some time after the next build runs and see if there is anything to see
g
bootc status
and 
rpm-ostree status
should provide that information
p
piggybacking here - is there a 
ujust
alternative to the above?
g
You can create some of your own systemd units to do this with timers. I can link you guys an example of how I handle it
m
I think the automatic updates are working. Today when I ran 
rpm-ostree status
, I had a new version staged
g
Cool!
m
I should check it as well in 10 days when I back home. Every time I had to run it manually despite the stage mood. Would be great to have a notification if there are new updates and if these have been successfully installed (maybe it should already happen but I rarely see these notifications). Also I have very instable internet connection and usually an update needs me to re run the upgrade command 3 4 times because unfortunately when the connection goes down the command stops working...
At least it doesn't re-start from zero
m
Taking a look at this again. Looking at your linked updates.yml, you have 4 items listed here, but in the source dir, I only see files for 
bootc-update
Copy code
files/bootc-update/
├── bootc-fetch-apply-updates.service
└── bootc-fetch-apply-updates.timer
I'm guessing it's because your base already includes what it needs for these ones :
Copy code
- ublue-update.timer
        - uupd.timer
        - rpm-ostreed-automatic.timer
Is that right?
The automatic updates WERE working fine for me and then stopped at some point recently.
I think it was right around when bluefin (which I'm using as my base) changed silverblue 42 from being its latest to its GTS
g
Yeah I disabled the ublue updater cause it was causing me issues. I just use the bootc one to update
masked
makes it so that it's disabled no matter who has it enabled
m
Hmm, okay, so as long as I copy that bootc-update dir from your files, I should be good to go, right?
As in, the rest of this updates.yml will work, there's not any other service/timer files from your config I'd need to track down
g
It's only for bootc, but yeah
m
Cool, I'll give that a shot
PreviousNext
Powered by