Dom0 update error | curl error (37) | code 127

[whoami]

My default dom0 update routine is not working anymore.

My settings:

• 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:

Update troubleshooting

Dom0 secure updates

Try manual update in dom0 …

sudo qubes-dom0-update

… 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

… returns

then checking the repodata folder:

[HPOA909]

Have you installed the qubes dom0 update pacjage in your apt cacher template? If not, that’s the problem at first place.

[whoami]

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.

[whoami]

Fixed, now

For others who might find this thread:

• check your overall setup and installation
  see: Debian-10-minimal Configuration - #94 by Sven
  and the official notes/apt-cacher-ng.md at master · unman/notes · GitHub
• check your qubes-core-agent-dom0-updates installation with:
  dpkg-query -l qubes-core-agent-dom0-updates
• check your dom0 update settings:
  → Q → Qubes Tools → Qubes Global Settings → qube defaults
  → Dom0 update qube: apt-cacher (or if you use another appVM i.e. firewall)

In my case the issue was that the Dom0 update qube setting was pointing to my firewall appVM instead of my apt-cacher appVM.

[unman]

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.

[whoami]

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?