Builder for QubesOS Alpine Template
Find a file
2024-02-08 10:57:52 -05:00
scripts scripts/04_install_qubes.sh: autostart qubes-updates-proxy-forwarder for apk proxy 2024-02-08 10:57:52 -05:00
.gitlab-ci.yml Build for Alpine v3.19 2023-12-07 19:30:25 -05:00
builder.conf Build for Alpine v3.19 2023-12-07 19:30:25 -05:00
Makefile.alpinelinux Ported rest of scripts for use by linux-template-builder 2023-08-25 17:44:09 -04:00
Makefile.builder Support different alpine versions 2023-08-26 17:14:13 -04:00
prepare-chroot-base Support different alpine versions 2023-08-26 17:14:13 -04:00
prepare-chroot-builder Ported rest of scripts for use by linux-template-builder 2023-08-25 17:44:09 -04:00
README.md Add README 2023-08-26 17:19:27 -04:00

qubes-builder-alpine

Upstream: https://lab.ilot.io/ayakael/qubes-builder-alpine

Description

This repository contains an implementation of a template builder for Alpine Linux for usage by qubes-builder. Packages are pulled from a community repo and packaged in an RPM that is installable by QubesOS.

Current state

Alpine Linux as a QubesOS template is still a work and progress. It is highly encouraged to make bug reports.

The yet-to-be-implemented list

Thus the following use cases are still not supported / tested:

  • QubesOS r4.2
  • Service VMs (sys-net, sys-usb, sys-firewall)
  • Firewall (not tested)
  • qubes-builder hooks (thus no dom0 template RPM yet, see here for progress)
  • apk proxying from within template (thus you must allow internet access to template to install packages)
  • qubes-vm-kernel-support Not adapted for use on Alpine yet, due to it providing a Dracut module. In most cases, it is not necessary as Qubes provides the kernel. This package is only neccessary when VM uses its own kernel, thus a hook is added to Dracut to generate the initrd for use within qubes.

Issues, recommendations and proposals

To report an issue or share a recommendation

Go here

To make a merge request

  • Fork the repo from Alpine's GitLab here
  • Clone your fork locally. (git clone $repo)
  • Make a branch with a descriptive name (git checkout -b $descriptivename)
  • Make the changes you want to see in the world, commit, and push to the GitLab's remote repo
  • Request a merge here