On umbrelOS 1.7.1, I manually recreated custom /etc/systemd/system/*.service files that were previously part of my setup but were removed after updating.
This also affected related customizations such as:
Cloudflare Tunnel setup
Host-level automation
Docker permissions/group membership changes that broke existing docker-based aliases/scripts
For example, commands that previously worked via docker aliases began returning permission denied errors until permissions were manually corrected.
After recreating these items, they work again temporarily. However, after a normal reboot, the custom service files and related changes are no longer present again.
Is this expected behavior in 1.7.1, or a persistence bug?
Yeah, this makes no sense to me at all on why they are doing this in the 1.7x versions. I understand trying to protect the OS but not completely not allowing customization???
At this time, I have no plans to upgrade off 1.5 until this is fix or a workaround becomes available.
And, if anyone comes up with a workaround to remove the “umbrelOS 1.7.2 is now availale to install” … I would sure be interested in that!
in my case, my little nuc box needs a special ethernet driver built (reaktek r8125) - umbrelos doesn’t properly support it out-of-box - but my previous (simple) steps to build the driver and install it no longer persist after reboot - meaning ethernet disappears.
THIS IS THE KEY:
sudo rugix-ctrl state overlay force-persist true
now i can do my driver build/install process and it survives rebooting.
then add a persistent repair hook (using /home/umbrel/umbrel/custom-hooks/pre-start) that reinstalls if driver disappears after an umbrel os update