When building archlinux packages and template using container executor (docker being the only one available atm), the env ARCHLINUX_MIRROR is not being used to create the mirrorlist file, resulting in slow speeds during package downloads.
Steps to reproduce
Install dependencies
Build docker container image
Run ARCHLINUX_MIRROR=http://mirror.com ./qb package fetch prep build
Expected behavior
ARCHLINUX_MIRROR should be used to create the mirrorlist file
Actual behavior
ARCHLINUX_MIRROR is not being used and the default mirrorlist file is being used
Additional info
Upon debugging, I see that the initial command sent to the executor during build step is the following:
which doesn't mention the https://github.com/QubesOS/qubes-builder-archlinux/blob/main/prepare-chroot-base script that did the ARCHLINUX_MIRROR logic, as well as doing some things that were originally handled in the qubes-builder-archlinux repository.
It has to be enlarged as this is true for any other _MIRROR variables. This is a known limitation because it has not been implemented yet in qubes-builderv2.
Qubes OS release
4.2
Brief summary
When building archlinux packages and template using container executor (docker being the only one available atm), the env
ARCHLINUX_MIRROR
is not being used to create the mirrorlist file, resulting in slow speeds during package downloads.Steps to reproduce
ARCHLINUX_MIRROR=http://mirror.com ./qb package fetch prep build
Expected behavior
ARCHLINUX_MIRROR should be used to create the mirrorlist file
Actual behavior
ARCHLINUX_MIRROR is not being used and the default mirrorlist file is being used
Additional info
Upon debugging, I see that the initial command sent to the executor during
build
step is the following:which doesn't mention the
https://github.com/QubesOS/qubes-builder-archlinux/blob/main/prepare-chroot-base
script that did theARCHLINUX_MIRROR
logic, as well as doing some things that were originally handled in thequbes-builder-archlinux
repository.