blob: 4843f8413ca12e42ee765aaa59ce4e0506bcfaf3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
# arch-boxes
[](https://github.com/archlinux/arch-boxes/actions)
Arch-boxes provides automated builds of the Arch Linux releases for
different providers and post-processors. Check the providers or post-processor sections if you want to know
which are currently supported.
## Dependencies
You'll need the following dependencies:
* packer (for basic usage)
* vagrant (for vagrant images)
* qemu (for libvirt provider support)
* virtualbox (for virtualbox support)
* VMware Workstation Pro (for vmware support)
## variables
Here is an overview over all variables you can set in `vagrant.json` or
`local.json`:
* `iso_url`: the url to the ISO. This can be an url or a filepath
beginning with `file://`
* `iso_checksum_url`: the url to the checksum file. This can be an url
or a filepath beginning with `file://`
* `iso_checksum_type`: this specifies the hashing algorithm for the
checksum.
* `disk_size`: this specifices the disk size in bytes.
* `memory`: this specifies the size of the RAM in bytes.
* `cpus`: this specifies the number of cores for your VM.
* `headless`: this sets GUI on or off.
* `vagrant_cloud_token`: here you can specify the vagrant cloud token for
uploading your box to the vagrantcloud. If you don't have a vagrant cloud
token you can ignore this variable. Without a token the boxes will be
built, but the upload step step will fail.
* `write_zeroes`: this variable is empty. if you set any string in this
variable it will fill the box with zeros to reduce the size. **DO NOT
use this if you are running a SSD. It will harm your SSDs lifetime**
* `boot_wait`: this specifies the time packer should wait for booting up
the ISO before entering any command.
## how to start the build process locally
If you want to build the boxes locally without uploading them to the Vagrant
cloud you need to edit the `local.json` before you start the build. set the
right `iso_url` and the right `iso_checksum_url`. Then you can start the build
for virtualbox only with the following command:
`packer build -only=virtualbox-iso local.json`
## how to start the build process for official builds
The official builds are done on our Arch Linux Buildserver.
`packer build vagrant.json`
## providers
* virtualbox-iso
* qemu/libvirt
* vmware-iso
## post-processors
* vagrant
## Troubleshooting
### Parallel build fails
If the parallel build fails this is mostly because the KVM device is
already occupied by a different provider. You can use the build option
`parallel=false` for building the images in a queue instead of parallel.
But don't be surprised that that the build process will take longer. Any
other option is to disable KVM support for all other providers except
one.
Start `packer` with `-parallel=false`:
`packer build -parallel=false vagrant.json`
|
