[arch-dev-public] Arch Linux Docker / Vagrant: Current situation

Christian Rebischke Chris.Rebischke at archlinux.org
Sun Jan 21 19:50:04 UTC 2018

On Sun, Jan 21, 2018 at 07:41:53PM +0100, Public mailing list for Arch Linux development wrote:
> It would be probably seen as more "official" if it was mentioned on our
> website.

Absolutly! I will see what I can do to bring that on our website.

> > My first goal has been to add some hypervisors, but due to
> > the fact that we have only libvirt and virtualbox in our repositories I
> > have dismissed this plan. The automated build process works fine so far
> > (except some issues with qemu[2] and the dependency on punctual iso
> > releases on soyuz. The latter should we definitly fix. Currently the iso
> > images are build manually. Can we automate this somehow? I really rely
> > on punctual releases otherwise the automated build will fail and
> > somebody needs to trigger the build again manually. Happened about 1-2
> > times..)
> This is something that would require a virtually offline box to be fully
> automated. For the time being, it sounds better to upgrade your vagrant
> image after first week of the month.

Actually I do this already. The systemd timer for the automated builds
is set on the 5th of each month (round about a week). Normally the ISO
was there on 1st or 2nd each month, but in the last months its more like
6th or 9th. I could move that timer on 14th, but I would definitly
prefer to have the vagrant boxes around the same date as we release our
ISO images.

> Also, any plans to expand the scope to support OpenStack, AWS and GCE?
> At the moment the scope sounds rather limited.

It's possible to build images for OpenStack, AWS and GCE, but as far as
I understand the docs for it we would need an OpenStack cloud for
OpenStack images, an AWS account for generating Amazon EC2 Images and a
Google Account for generating GCE Images[1], because the packer connects
to these services to generate the image.

> Can you actually give more details how it's going to look like?
Sangy worked on this. He explained it one day, but It's already some
months ago. I hope he will attend our discussion here and give us a
short summary about that process.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20180121/83c9b4b1/attachment.asc>

More information about the arch-dev-public mailing list