- 08 Nov, 2020 3 commits
-
-
Kristian Klausen authored
I'm not sure polkit is needed in the vagrant images, but it is definitely not needed in the cloud-image.
-
Kristian Klausen authored
-
Kristian Klausen authored
It has never be enabled, makes zero sense in a cloud-image and isn't used by vagrant.
-
- 06 Nov, 2020 1 commit
-
- 14 Oct, 2020 1 commit
-
-
Kristian Klausen authored
Even though the system isn't booted, a machine-id is generated when systemd is installed (by the .install script). Fixes: 0b60f5a4 ("Remove "remove machine-id" logic") Fix #117
-
- 12 Oct, 2020 4 commits
-
-
Kristian Klausen authored
-
Kristian Klausen authored
-
Kristian Klausen authored
-
Greyson Christoforo authored
-
- 28 Sep, 2020 4 commits
-
-
Sven-Hendrik Haase authored
In my tests this gains us about 10MB.
-
Sven-Hendrik Haase authored
-
Sven-Hendrik Haase authored
-
Sven-Hendrik Haase authored
We still have the problem where the partition table or device appears too late. Hopefully this fixes it.
-
- 27 Sep, 2020 2 commits
-
-
Sven-Hendrik Haase authored
-
Kristian Klausen authored
Fix #114
-
- 26 Sep, 2020 4 commits
-
-
Sven-Hendrik Haase authored
-
netctl is only required by vagrant < v2.2.10
-
Python was added due to DevOps demands (Ansible). linux-headers is not needed and I'm not sure why it was added. Fix #111
-
Kristian Klausen authored
-
- 02 Sep, 2020 2 commits
-
-
Kristian Klausen authored
-
Kristian Klausen authored
... and use readonly, local and adding a few more comments.
-
- 30 Aug, 2020 7 commits
-
-
Kristian Klausen authored
-
Kristian Klausen authored
A machine-id is never generated, as the system isn't booted.
-
Kristian Klausen authored
-
Kristian Klausen authored
-
Kristian Klausen authored
-
Kristian Klausen authored
-
Kristian Klausen authored
Using actual VMs to build VMs is slow and error-prone (you need to use VNC to see what is going on, and booting takes over +110 seconds as we wait to be sure Arch Linux is ready). build.sh can build all three images in ~135 seconds (assuming all the packages is cached), we still need to use a VM for the actually building in GitLab CI (as that is the only safe way it can be done at the moment), which is a bit slower (~22 min vs ~13 min (Packer)), but that isn't really a big issue. In the future we can hopefully switch to Kate Containers[1] and reduce the build time significantly. [1] infrastructure#108
-