March 2, 2023, 2:08pm
My default dom0 update routine is not working anymore.
Apt-Cacher configured and works for templateVM updates
Disposable firewall and network
Global Settings: dom0 update qube is set to use disposable firewall (firewall-dvm)
Following the recommendations:
“Failed to synchronize cache for repo” errors when updating Fedora templates This is general Fedora issue, not a Qubes-specific issue. Usually, this is due to network problems (especially if downloading updates over Tor) or problems with the download...
Reasons for Dom0 updates Normally there should be few reasons for updating software in Dom0. This is because there is no networking in Dom0, which means that even if some bugs will be discovered e.g. in the Dom0 Desktop Manager, this really is not a...
Try manual update in dom0 …
… the firewall-dvm terminal pop-up window returns:
sh: 1: /usr/lib/qubes/qubes-download-dom0-updates.sh: not found
Fetching updates failed with code 127; press Enter to exit
Try dnf update in dom0
sudo dnf update
then checking the repodata folder:
Have you installed the qubes dom0 update pacjage in your apt cacher template? If not, that’s the problem at first place.
March 2, 2023, 4:06pm
No, only this:
notes/apt-cacher-ng.md at master · unman/notes · GitHub
In template-cacher install the software, by running as root:
apt-get install qubes-core-agent-networking apt-cacher-ng
systemctl mask apt-cacher-ng
Shut down template-cacher.
March 15, 2023, 12:58pm
For others who might find this thread:
In my case the issue was that the
Dom0 update qube setting was pointing to my firewall appVM instead of my apt-cacher appVM.
March 16, 2023, 10:26am
I do not recommend use of apt-cacher-ng with dom0 updates, if only
because dom0 fedora is eol and there is no point in caching updates
which cannot be applied elsewhere.
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
March 16, 2023, 4:32pm
You mean that I should install
qubes-core-agent-dom0-updates on my deb-11-m-firewall-dvm template and point the
Dom0 update qube to my firewall-dvm (instead of apt-cacher appVM)? …or should I use a non-dvm appVM instead?