This is the error code I received after trying to install.
Traceback (most recent call last):
File “/usr/bin/qvm-template-postprocess”, line 5, in
sys.exit(main())
^^^^^^
File “/usr/lib/python3.11/site-packages/qubesadmin/tools/qvm_template_postprocess.py”, line 449, in main
loop.run_until_complete(post_install(args))
File “/usr/lib64/python3.11/asyncio/base_events.py”, line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/site-packages/qubesadmin/tools/qvm_template_postprocess.py”, line 314, in post_install
import_root_img(vm, args.dir)
File “/usr/lib/python3.11/site-packages/qubesadmin/tools/qvm_template_postprocess.py”, line 102, in import_root_img
raise qubesadmin.exc.QubesException(
qubesadmin.exc.QubesException: template.rpm symlink not found for multi-part image, using up-to-date qvm-template install ... should help
ERROR: Command ‘[‘qvm-template-postprocess’, ‘–really’, ‘–no-installed-by-rpm’, ‘post-install’, ‘alpine318’, ‘/var/tmp/tmpjifu34ic/var/lib/qubes/vm-templates/alpine318’]’ returned non-zero exit status 1.
I did some research, and it seems the template installer thinks there’s missing parts of the file. I have no idea how to fix.
Hey all, I forgot I had an account here! I made the template referenced by OP. I see there’s an appreciation for my work, thanks for y’all’s interest! I’d be happy to get this fixed up for more official inclusion. I’ve yet to identify a clear way to get this template supported along the same lines as Arch Linux. At the minimum, I’ll maintain the packages and the RPM, and if any of y’all find (and fix issues) you can share them on here or on the GItHub issues page, I’ll have them integrated. I answer more quickly on the Github page, but I’ll try to keep an eye on the forums.
Thank you for your work, yesterday I switched from Alpine-3.19 to 3.20 without any problem (template update with the 3.20 repository, not the new 3.20 template rpm).
Of note, I’ve fixed a bug with qubes-usb-proxy which broke attaching devices to the Alpine AppVM. Incidently, this seems to also fix using Alpine Linux as a base for sys-usb. I’m working on porting GitHub - QubesOS/qubes-app-linux-input-proxy, but I’m not sure how to port the systemd services to openrc.
(edit: a package for the input proxy is already available via qubes-input-proxy, but it wont automatically spawn the proxy process since it does that via udev and systemd. It’s available via the repo though, for those who wish to figure out an openrc implementation)
For those on an edge template who lost access, you can fix your template by updating it through sudo xl console template-name and apk update; apk upgrade and restarting your template.
I have a ton of qubes, so a much lighter-weight template would be extremely helpful for my workflow. Thanks for this, hoping to see it in the Template Manager soon!
With the first release candidate out for Alpine 3.21, I’ve built the packages against it. You can already upgrade to this release, although you must follow these steps first. Not doing so will break your template! There is an issue with upgrading qubes-libvchan-xen which requires manual intervention.
Option A
Change release of repos in /etc/apk/repositories to 3.21
Temporarily attach your template to a network qubes (i.e sys-firewall)
Change release of repos in /etc/apk/repositories to 3.21
apk upgrade -a
Detach template from the network qubes
What is happening?
Alpine’s packager apk installs packages while downloading. This makes apk faster than other package keepers. To avoid having templates connected to the internet, apk is setup to go over a proxy.
The problem is that when upgrading qubes-libvchan-xen, which is a dependency of this proxy, apk upgrades xen first without downloading the package. Thus, when upgrading qubes-libvchan-xen, download / installation fails, which then breaks the proxy. Thus, qubes-libvchan-xen can never be downloaded, and thus your template is in a broken non-bootable state.
The above interventions either forces installation of qubes-libvchan-xen before upgrading xen, or removes the need for the proxy by having the template attached to a network qubes.
however I have no idea how to compile these, is this where qubes builder comes in? Because I was able to get alpine321 template going without using anything but downloading the .rpm.
Would very much appreciate a link to how to build and install the necessary aports
thank you so much, the effort is incredible and I am so happy to have an alpine template, I hope it becomes official.
Hi @cubit ,
the CLI (Command Line Interface) qvm-copy / qvm-move tools work with the Alpine Template, so it’s an alternative to the GUI (Graphical User Interface) menu entries in the File Manager.
Resources if you don’t know the qvm-copy / qvm-move commands:
Thank you this is great. I still assumes the aports are not included by default? 1.Is there a guide for importing them to the Alpine template?
It also may just be user error, but I cannot get a DVM of an alpine app cube to show apps in the application finder like "Firefox (DVM’ that automatically starts the selected app in a new disposable, is this feature included? (For example ```
[user@dom0 ~]$ qvm-prefs DVM-NAME template_for_dispvms True
[user@dom0 ~]$ qvm-features DVM-NAME appmenus-dispvm 1
produce an error: ‘no such property’
I changed the AlpineTemplate repos to EDGE, is this going to pose a problem?
Maybe better to report on your repo but: opening one file explorer in an Alpine template is fine, but attempting to spawn another causes both to close. opening further file explorer windows does not work until restarting the vm.
I launch my Alpine DVM Firefox with a keyboard shortcut mapped to : qvm-run --dispvm dvm-alpine /usr/bin/firefox.
My Qubes main menu displays my dvm-alpine and the applications listed by qvm-features dvm-alpine menu-items . Did you add the Firefox application in Qube Manager/your DVM/Settings/Applications tab?
Please, do the checks and read the official documentations:
. I just upgraded from Alpine 3.20.5 to 3.21.2.