Bug#1041900: cloud.debian.org: please publish arm64 vagrant boxes

Hi Lucas, On Wed, Aug 02, 2023 at 10:38:24PM -0700, Ross Vandegrift wrote: > The system tests need some easy fixes. The end to end test tries to boot the > image on the native arch. It probably needs a feature to check if qemu is > needed. Time permitting, I plan to look at these in the next

Bug#1041900: cloud.debian.org: please publish arm64 vagrant boxes

Hi Lucas, On Wed, Jul 26, 2023 at 08:53:29PM +0200, Lucas Nussbaum wrote: > On 24/07/23 at 22:00 -0700, Ross Vandegrift wrote: > > I've been in touch with folks from the kdevops project [1]. They are > > looking > > for more vagrant images for arm64. Would it be possible to publish the > >

Bug#1041900: cloud.debian.org: please publish arm64 vagrant boxes

Hi Ross, On 24/07/23 at 22:00 -0700, Ross Vandegrift wrote: > I've been in touch with folks from the kdevops project [1]. They are looking > for more vagrant images for arm64. Would it be possible to publish the arm64 > boxes that debian-vagrant-images can build? > > I started looking into

Bug#1041900: cloud.debian.org: please publish arm64 vagrant boxes

Package: cloud.debian.org Severity: wishlist User: cloud.debian@packages.debian.org Usertags: vagrant image X-Debbugs-Cc: rvandegr...@debian.org Hello, I've been in touch with folks from the kdevops project [1]. They are looking for more vagrant images for arm64. Would it be possible to

Re: Nightly Builds and Continous Delivery for Vagrant Boxes plans

Le 06/06/2020 à 11:50, Bastian Blank a écrit : > On Sat, Jun 06, 2020 at 11:00:36AM +0200, Emmanuel Kasper wrote: >> Unfortunately the 250MB limit of artifacts prevent building a pipeline >> with multiple stages like >> create .box from raw -> test -> upload >> as I hit the artifact limit size

Re: Nightly Builds and Continous Delivery for Vagrant Boxes plans

On Sat, Jun 06, 2020 at 11:50:39AM +0200, Bastian Blank wrote: > On Sat, Jun 06, 2020 at 11:00:36AM +0200, Emmanuel Kasper wrote: > > Unfortunately the 250MB limit of artifacts prevent building a pipeline > > with multiple stages like > > create .box from raw -> test -> upload > > as I hit the

Re: Nightly Builds and Continous Delivery for Vagrant Boxes plans

On Sat, Jun 06, 2020 at 11:00:36AM +0200, Emmanuel Kasper wrote: > Unfortunately the 250MB limit of artifacts prevent building a pipeline > with multiple stages like > create .box from raw -> test -> upload > as I hit the artifact limit size between each of these stages. Please take a deeper look

Re: Nightly Builds and Continous Delivery for Vagrant Boxes plans

On 6/2/20 10:49 PM, Emmanuel Kasper wrote: Hi Now that I have working vagrant boxes with FAI, I'm starting to look at nightly builds and continuous delivery of boxes to the vagrant cloud (remember the "vagrant cloud" is just a disk image registry. The VMs are run locally on your infr

Nightly Builds and Continous Delivery for Vagrant Boxes plans

Hi Now that I have working vagrant boxes with FAI, I'm starting to look at nightly builds and continuous delivery of boxes to the vagrant cloud (remember the "vagrant cloud" is just a disk image registry. The VMs are run locally on your infrastructure) Nightly Build: --

Followup on Vagrant Boxes with debian cloud images

istributions is a bit overkill to do at home on a ADSL connection. So after a month of pushing things here or there I came to the conclusion that it should be easier if I manage vagrant boxes in a fork of debian-cloud-images I noticed three things with makes creating vagrant boxes in the deb

Bug#940587: cloud.debian.org: additional Vagrant boxes with puppet/ansible pre-installed?

Am 18.09.2019 um 21:08 schrieb Geert Stappers: On Wed, Sep 18: On 2019-09-18 1:36 a.m., Geert Stappers wrote: On Tue, Sep 17, 2019 at 10:52:54AM -0400, Gabriel Filion wrote: vagrant boxes images that would have puppet/ansible pre-installed Hello Gabriel ! Thanks for your interest

Bug#940587: cloud.debian.org: additional Vagrant boxes with puppet/ansible pre-installed?

On Wed, Sep 18: > On 2019-09-18 1:36 a.m., Geert Stappers wrote: > > On Tue, Sep 17, 2019 at 10:52:54AM -0400, Gabriel Filion wrote: > >> vagrant boxes images that would have puppet/ansible pre-installed > > There is https://cloudinit.readthedocs.io/en/latest/ > &

Bug#940587: cloud.debian.org: additional Vagrant boxes with puppet/ansible pre-installed?

Hi, On 2019-09-18 1:36 a.m., Geert Stappers wrote: > On Tue, Sep 17, 2019 at 10:52:54AM -0400, Gabriel Filion wrote: >> I was wondering if folks maintaining the vagrant boxes would be willing to >> publish additional images that would have puppet/ansible pre-installed with >>

Bug#940587: cloud.debian.org: additional Vagrant boxes with puppet/ansible pre-installed?

On Tue, Sep 17, 2019 at 10:52:54AM -0400, Gabriel Filion wrote: > 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? I a

Bug#940587: cloud.debian.org: additional Vagrant boxes with puppet/ansible pre-installed?

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

Re: systemd-networkd and networking service in vagrant boxes

Hello Emmanuel, On 2019-06-08 11:24 a.m., Emmanuel Kasper wrote: This is unfortunately a known behaviour and also a bug. VirtualBoxes images use ifupdown for network configuration, and Libvirt images use systemd-networkd, due to a bug in vmdeboostrap. Can you submit a bug report against the

Re: systemd-networkd and networking service in vagrant boxes

ebops/debops/issues/629 > [1] https://debops.org > [2] https://github.com/debops/debops/issues/629#issuecomment-499774400 Hi Nicolas Thanks for your interest with the debian vagrant boxes, and thanks for reaching upstream, always a nice thing to do :) ( i read your bug report in details ) >

systemd-networkd and networking service in vagrant boxes

Hello, I'm using Vanilla Debian base boxes from https://app.vagrantup.com/debian/ with libvirt and Virtualbox providers. I noticed a difference between providers for the same box (debian/stretch64). * with libvirt provider, `systemd-networkd` service is enabled and started after first boot

Re: Updated Vagrant Boxes for Wheezy

> Message transféré > Sujet : Debian Wheezy: Vagrant boxes > Date : Thu, 30 May 2019 13:29:25 +0200 > De : Alexander Nitsche | e-pixler NEW MEDIA GmbH > > Pour : m...@debian.org > > Hello Emmanuel, > > i am Alex, a PHP developer from Berli

Updated Vagrant Boxes for Wheezy

Forwarding to debian-cloud with original author agreement, so we can have an open discussion. Message transféré Sujet : Debian Wheezy: Vagrant boxes Date : Thu, 30 May 2019 13:29:25 +0200 De : Alexander Nitsche | e-pixler NEW MEDIA GmbH Pour : m...@debian.org Hello Emmanuel

Re: Vagrant boxes for 9.5.0

Le 19/08/2018 à 11:39, Carlos Rodrigues a écrit : > Hi there, > > Is there any reason for the "debian/stretch64" 9.4.0 boxes to remain > tagged as the currently released version even though 9.5.0 has been > there for a month? > > Best regards, > I just released 9.5.0 for virtualbox and

Re: Vagrant boxes for 9.5.0

Am 19. August 2018 11:39:45 MESZ schrieb Carlos Rodrigues : >Hi there, > >Is there any reason for the "debian/stretch64" 9.4.0 boxes to remain >tagged as the currently released version even though 9.5.0 has been >there for a month? > >Best regards, > >-- >Carlos Rodrigues Hi Carlos Thanks for

Re: Problem creating Vagrant boxes

Hi Emmanuel, fai-cloud-images is rather a work in progress for Vagrant Images, you> should look at debian-vm-templates for the working stuff. OK, but my plan is to merge the config_space of fai-cloud-images into our existing FAI config space to create custom VM images that match our existing

Re: Re: Problem creating Vagrant boxes

Hi, I couldn't reproduce the DNS resolution problem anymore. They both use the same deb.debian.org package repository so when I noticed this problem about ~1 month ago I ran "sudo apt update" on the 9.2.0 image it wasn't able to fetch the packages but with 9.1.0 it was. I have no idea what made

Re: Problem creating Vagrant boxes

Le 18/11/2017 à 23:50, Joonas Kylmälä a écrit : > I had also the DNS resolution problem with the latest Debian Stretch > VirtualBox image, 9.2, which was downloaded from the Vagrant Cloud. Hi Joonas Before uploading the boxes, we run a test suite, which among other things, downloads a package

Re: Problem creating Vagrant boxes

I had also the DNS resolution problem with the latest Debian Stretch VirtualBox image, 9.2, which was downloaded from the Vagrant Cloud. Emmanuel Kasper: > Le 17/11/2017 à 12:53, Christopher Huhn a écrit : >> Dear Debian Cloud Team, >> >> on the occasion of re-investigating vagrant I stumpled

Re: Problem creating Vagrant boxes

Le 17/11/2017 à 12:53, Christopher Huhn a écrit : > Dear Debian Cloud Team, > > on the occasion of re-investigating vagrant I stumpled upon the > debian-vm-templates and the fai-cloud-images git repos. > Esp. the latter is exactly what I was looking for. Nice!> Anyhow I have the > following

Problem creating Vagrant boxes

Dear Debian Cloud Team, on the occasion of re-investigating vagrant I stumpled upon the debian-vm-templates and the fai-cloud-images git repos. Esp. the latter is exactly what I was looking for. Nice! Anyhow I have the following problem (on a Stretch system) with both `make

Re: Vagrant Boxes

Hi, Emmanuel Kasper: > I see also that you expressed interess to create Vagrant Boxes for > Docker. We haven't start anything there but I would be interesting to > hear if such a thing is possible with fai[1] the tool we evaluate to use > in the future for all boxes. > If you want

Re: Vagrant Boxes

t up. I see also that you expressed interess to create Vagrant Boxes for Docker. We haven't start anything there but I would be interesting to hear if such a thing is possible with fai[1] the tool we evaluate to use in the future for all boxes. If you want to play around with that, you can clone the gi

Re: Vagrant Boxes

Antonio Terceiro: > https://app.vagrantup.com/debian/boxes/stretch64 > > ^ libvirt and lxc are already available. what exactly are you missing? Latest version of Jessie (and Testing) is missing them. I see there has been lxc and libvirt previously so I thought maybe something happened (like some

Vagrant Boxes

Hi, In Vagrant Cloud I see mostly Virtualbox Vagrant Boxes. Can I somehow help with getting some free providers working with the image, like libvirt, lxc or docker? Is the problem that there is no packer setup for the other Vagrant providers? So if I would create those packer setups and send

Bug#868679: marked as done (cloud.debian.org: Multiple identical vagrant boxes appear as the same machine to libvirt's dnsmasq dhcp provider)

Your message dated Thu, 27 Jul 2017 17:33:53 -0300 with message-id <20170727203353.sjz7v32dkqn44...@debian.org> and subject line Re: Bug#868679: (no subject) has caused the Debian Bug report #868679, regarding cloud.debian.org: Multiple identical vagrant boxes appear as the same m

Bug#868679: Re: Bug#868679: cloud.debian.org: Multiple identical vagrant boxes appear as the same machine to libvirt's dnsmasq dhcp provider

ibera.cc> > Date: 18/07/2017 5:14 p.m. (GMT+00:00) > To: Jan Grant <j...@ioctl.org>, 868...@bugs.debian.org, > sub...@bugs.debian.org > Subject: Re: Bug#868679: cloud.debian.org: Multiple identical vagrant boxes > appear as the same machine to libvirt's dnsmasq dhcp provider > &g

Bug#868679: cloud.debian.org: Multiple identical vagrant boxes appear as the same machine to libvirt's dnsmasq dhcp provider

s.debian.org, sub...@bugs.debian.org Subject: Re: Bug#868679: cloud.debian.org: Multiple identical vagrant boxes appear as the same machine to libvirt's dnsmasq dhcp provider On 07/17/2017 05:16 PM, Jan Grant wrote: > The box image should not include those files (it suffices to delete them prior

Bug#868679: cloud.debian.org: Multiple identical vagrant boxes appear as the same machine to libvirt's dnsmasq dhcp provider

On 07/17/2017 05:16 PM, Jan Grant wrote: > The box image should not include those files (it suffices to delete them prior > to packaging the image). This causes each instance to mint its own new > UUID, which in turn results in distinct client-ids being supplied by > systemd. It does not seem to

Bug#868679: cloud.debian.org: Multiple identical vagrant boxes appear as the same machine to libvirt's dnsmasq dhcp provider

Package: cloud.debian.org Severity: important Tags: newcomer Dear Maintainer, * What led up to the situation? I've been having problems using the supplied vagrant boxes in more complex setups (where a Vagrantfile brings up more than one identical machine). They effectively end up stealing

Vagrant Boxes images for Stretch released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi List Antonio and I uploaded Vagrant Boxes images for the Stretch release this week end, enjoyable at https://atlas.hashicorp.com/debian/boxes/stretch64 more info at https://wiki.debian.org/Teams/Cloud/VagrantBaseBoxes Thanks for the hard

Re: Vagrant Boxes images release for Stretch

On Fri, Jun 16, 2017 at 11:18:33AM +0200, Emmanuel Kasper wrote: > Hi Lists > I will rebuild and upload Vagrant Boxes images on Sunday 18 June for the > VirtualBox provider. I build from CD so I need the CD images to be > already available on the webs. > So it should be right in

Vagrant Boxes images release for Stretch

Hi Lists I will rebuild and upload Vagrant Boxes images on Sunday 18 June for the VirtualBox provider. I build from CD so I need the CD images to be already available on the webs. So it should be right in time for Ana's blog post on Tuesday. I'll be around in #debian-cloud on Sunday to report my

Bug#863580: cloud.debian.org: Vagrant boxes randomly fail to come up when additional networks are configured

Le 30/05/2017 à 21:46, Branko Majic a écrit : > On Tue, 30 May 2017 21:23:58 +0200 > Emmanuel Kasper wrote: > >> Than you for the detailed bug report. >> >> I understand the unstable network card ordering can perturbate the >> network config if the NIC is assigned the name eth1

Bug#863580: cloud.debian.org: Vagrant boxes randomly fail to come up when additional networks are configured

On Tue, 30 May 2017 21:23:58 +0200 Emmanuel Kasper wrote: > Than you for the detailed bug report. > > I understand the unstable network card ordering can perturbate the > network config if the NIC is assigned the name eth1 instead of eth0. > But I am wondering why is that

Bug#863580: cloud.debian.org: Vagrant boxes randomly fail to come up when additional networks are configured

> After comparing the files in two boxes, turned out that > debian/contrib-jessie64 defines different network adapter type for > first network adapter and remaining ones (82540EM vs Am79C973). This > probably results in somewhat random ordering in the VM itself when > adapters are being named.

Bug#863580: cloud.debian.org: Vagrant boxes randomly fail to come up when additional networks are configured

Package: cloud.debian.org Severity: important Dear Maintainer, When additional networks are configured in Vagrantfile, this can result in Vagrant boxes randomly failing while bringing them up. Issue occurs both with debian/jessie64 and debian/contrib-jessie64. Reproduction steps: 1. Install

Re: Vagrant boxes debian 32 bits

Hi Emmanuel, Le vendredi 24 février 2017, Emmanuel Kasper <m...@debian.org> a écrit : > Hi Romain > > >> On 02/23/2017 12:39 AM, Romain Garbage wrote: > >>> Hello, > >>> > >>> I would like to know if the TeamCloud plans to also provide

Re: Vagrant boxes debian 32 bits

Hi Romain >> On 02/23/2017 12:39 AM, Romain Garbage wrote: >>> Hello, >>> >>> I would like to know if the TeamCloud plans to also provide 32 bit images >>> of Debian as Vagrant boxes on Atlas ? >>> >>> If it is of inter

Re: 32 bits Jesssie Vagrant boxes ?

Hi Manu. Emmanuel Kasper writes: > Le 20/01/2017 à 18:45, Olivier Berger a écrit : >> Hi. >> >> AFAICS on https://atlas.hashicorp.com/debian there are no 32 bits i686 >> stable/jessie images available for Vagrant. >> >> Maybe that'd be important for VirtualBox so that one may

Re: 32 bits Jesssie Vagrant boxes ?

Le 20/01/2017 à 18:45, Olivier Berger a écrit : > Hi. > > AFAICS on https://atlas.hashicorp.com/debian there are no 32 bits i686 > stable/jessie images available for Vagrant. > > Maybe that'd be important for VirtualBox so that one may test particular > environments where 64 bits isn't suitable

32 bits Jesssie Vagrant boxes ?

Hi. AFAICS on https://atlas.hashicorp.com/debian there are no 32 bits i686 stable/jessie images available for Vagrant. Maybe that'd be important for VirtualBox so that one may test particular environments where 64 bits isn't suitable (for instance if meant to be run on end-user machines only

Re: Debian Vagrant boxes and Virtualbox

Hi Chris, On 22 February 2016 at 04:51, Chris Fordham wrote: > Needs to go on wiki? That would be nice. Teams/Cloud/VagrantBaseBoxes[1] is the first result on Google when someone searchs for "debian vagrant" (without quotes), but there's no mention to the

Re: Debian Vagrant boxes and Virtualbox

n Mon, Feb 22, 2016 at 3:22 AM Emmanuel Kasper <emman...@libera.cc> > wrote: > >> Le 21/02/2016 22:18, Benjamin Schubert a écrit : >> > Hi, >> > >> > First of all, thanks a lot for your awesome work on Debian vagrant >> boxes. >> > They

Re: Debian Vagrant boxes and Virtualbox

; > First of all, thanks a lot for your awesome work on Debian vagrant boxes. > > They work really well ! > > > > I however stumble on a problem with the rsync synchronization used now on > > these boxes and I'd need to use the Virtualbox shared folder feature. > > > &

Bug#787298: providing base vagrant boxes that both minimal and featureful

On Tue, Jun 02, 2015 at 08:31:13AM +1000, Chris Fordham wrote: On 02/06/2015 7:12 AM, Emmanuel Kasper emman...@libera.cc wrote: The other point is that including (either) provisioner takes us further from the standard Debian image. BTW, Was is actually a standard Debian image ? To

Bootstrap-vz to produce Debian testing Vagrant boxes

Hello all, Allow me to apologize for any mistakes as English is not my native language. I'm currently working on creating a vagrant basebox using Debian and I plan to use bootstrap-vz. Is the script able to create a Debian testing Vagrant VM? Is there a huge difference between the master and

Re: Bootstrap-vz to produce Debian testing Vagrant boxes

Hi Stéphane, Allow me to apologize for any mistakes as English is not my native language. Don't worry. There is a lot of non-native English speakers here. I guess that is fine as long as we could understand each other (and use a spell checker, of course - but we should do that for any language

Re: providing official vagrant boxes of wheezy?

2013/10/17 Adam Bolte abo...@systemsaviour.com On Thu, Oct 17, 2013 at 09:59:04AM +0600, Anders Ingemann wrote: On Thursday, October 17, 2013, Antoine Beaupré wrote: How hard would it be for the debian project to provide official vagrant images of wheezy alongside the regular .ISO

providing official vagrant boxes of wheezy?

How hard would it be for the debian project to provide official vagrant images of wheezy alongside the regular .ISO images? Ubuntu has this place where they publish a bunch of similar images, how about us? http://cloud-images.ubuntu.com/ A. PS: please cc. -- It is a miracle that curiosity

Re: providing official vagrant boxes of wheezy?

On Thu, Oct 17, 2013 at 09:59:04AM +0600, Anders Ingemann wrote: On Thursday, October 17, 2013, Antoine Beaupré wrote: How hard would it be for the debian project to provide official vagrant images of wheezy alongside the regular .ISO images? Ubuntu has this place where they publish a