Hi there,

I've been holding back on using the debian/* boxes with vagrant mostly since
there's no puppet pre-installed in the boxes.

I know that, as documented in the wiki, I can install puppet with a shell
provisioner, but doing that on every boot makes things very much slower.

I could also start from the vanilla box, install puppet and then repackage
into a new box locally, but the point of using a public box is so that other
contributers can start with exactly the same environment.

I'm also aware that pre-installing those would make the images much bigger,
and I can see the point of having a very tiny completely vanilla debian image.

I was wondering if folks maintaining the vagrant boxes would be willing to
publish additional images that would have puppet/ansible pre-installed with
the debian packages from each release's package repository?

cheers!

I also don't understand how cloudinit works.

There is https://cloudinit.readthedocs.io/en/latest/
But it lacks what it makes it tick.

Nowhere is documented
* how it starts (what triggers the start)
* how "client" finds "server"
* why "client" trusts "server"


Groeten
Geert Stappers

Hi,

I don't quite understand how this question is related to building
Vagrant boxes.

According to the documentation[0] the boxes are generated using a Packer
template, and cloudinit is mentioned nowhere on that wiki page.

[0]: https://wiki.debian.org/Teams/Cloud/VagrantBaseBoxes#Build_process

On Wed, Sep 18:
} I don't quite understand how this is related to building Vagrant boxes.

It isn't indeed.  Now the uncensored version:

|It feels wrong to put specific orchestartion components in all images
|when one knowns there is a generic component (cloudinit) that solves
|the problem. Sadly is cloudinit poorly documented.
|So now to choose from two problems.
|My choice would be going for understanding "cloudinit"


Good luck with your approach.


Regards
Geert Stappers

Am 18.09.2019 um 21:08 schrieb Geert Stappers:
Hello Gabriel !

Thanks for your interest for the vagrant boxes.

Creating a different box for a single debian package is overkill IMHO, 
so for your use case, I suggest to add via apt-get puppet to a running
instance of the box, then its only a single command (vagrant repackage)
and you can distribute it via http or a shared file system ( the boxes
don't need to be on the vagrant cloud)