arch-boxes

• Vagrant Cloud
• Download latest artifacts

Arch-boxes provides automated builds of the Arch Linux releases for different providers and formats.

Usage

Vagrant

If you're a vagrant user, you can just go to our Vagrant Cloud page and follow the instructions there.

Basic image

If you want to run Arch Linux locally in a VM (ex: for quick ad hoc testing), you can use our basic image, which comes preconfigured with a

arch

arch

Arch-Linux-x86_64-basic-xxxxxxxx.xxxx.qcow2

Cloud image

If you want to run Arch Linux in the cloud, you can use our cloud-image, which is preconfigured to work in most cloud environments. It is built daily and can be downloaded here (

Arch-Linux-x86_64-cloudimg-xxxxxxxx.xxxx.qcow2

The default user is

arch

If you are running the cloud-image with QEMU, it can in some cases* be beneficial to run the QEMU guest-agent. This can be done with the following user-data: ```yaml

cloud-config

packages: - qemu-guest-agent runcmd: - [ systemctl, daemon-reload ] - [ systemctl, enable, qemu-guest-agent ] - [ systemctl, start, qemu-guest-agent ] ``` *ex: when using Proxmox or oVirt. Please be aware, that the agent basically gives the host root access to the guest.

Be advised, however, that our automatic builds are cleaned up after a few days so you can't hard-code a specific image version anywhere.

You can use this snippet to always get the most recent image and check its integrity (you need to install

hq

most_recent=$(curl -Ls 'https://gitlab.archlinux.org/archlinux/arch-boxes/-/jobs/artifacts/master/browse/output?job=build:secure' | grep cloudimg | grep -vi sha256 | hq a attr href | sed "s|artifacts/file|artifacts/raw|")
curl -LO  "https://gitlab.archlinux.org$most_recent"{,.SHA256}
sha256sum -c $(basename $most_recent).SHA256

Development

Dependencies

You'll need the following dependencies:

• vagrant (for vagrant images)
• qemu
• libisoburn

How to build this

The official builds are done in our Arch Linux GitLab CI.

./build-host.sh

Development workflow

Merge requests and general development shall be made on the

master

We have CI in place to build all images even for merge requests.

Release workflow

Releases are done automatically via GitLab CI schedule. No manual intervention is required or desired.

Checking cloud-init support in our cloud image:

Please see the example in

man cloud-localds