Official Debian Images for Vagrant

Hello Cloud ! I am maintaining Debian images for Vagrant, a kind of Virtualbox environment manager (see vagrantup.com for details and https://packages.debian.org/sid/vagrant ) I host these created images here: http://subsole.org/vanilladebianbox Now the folks behind Vagrant are going to host an

Re: Official Debian Images for Vagrant

> As bootstrap-vz is used for other images and helps to reproduce image > creation for multiple providers, I would personally prefer to use > bootstrap-vz for official images. I had a look last summer at different ways to provide Virtualbox with some folks from the neurodebian team (see http://lis

Re: building (official) debian images for atlas (formerly vagrantcloud)

Hello Jan I just uploaded two unofficial Debian boxes on Atlas today, and then I noticed your mail :) I registered the "debian" account on Atlas, when Hashicorp started Vagrancloud so one can get the boxes quickly with: vagrant init debian/jessie64 So as you might guess I'm also interested in ha

Re: building (official) debian images for atlas (formerly vagrantcloud)

Le 24/04/2015 17:24, Olivier Berger a écrit : > Emmanuel Kasper writes: > >> Hello Jan >> >> I just uploaded two unofficial Debian boxes on Atlas today, and then I >> noticed your mail :) > > Again (see https://lists.debian.org/debian-cloud/2014/07/msg00046

Re: building (official) debian images for atlas (formerly vagrantcloud)

> Am I right in saying that packer brings in the main benefit of not > setting a fixed size for the disks, which is problematic with > bootstrap-vz (as Jan experienced) ? To the best of my knowledge you do set a disk size in a packer template, but then the disk image grows as you fill the vm with

Re: building (official) debian images for atlas (formerly vagrantcloud)

> I experienced a partition/disk limit of some kind when I tried to create > a base box for FusionForge with bootstrap-vz, but I hit some limit. > > I then changed for a packer approach, which was more flexible... but I > forgot the exact details unfortunately (twins born in between and lack > of

Git repo for debian VM templates

tform) [1] https://wiki.debian.org/Teams/Cloud/VagrantBaseBoxes Emmanuel Kasper -- To UNSUBSCRIBE, email to debian-cloud-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5540d4d4.8010...@libera.cc

Re: Git repo for debian VM templates

Hi all Le 30/04/2015 10:18, Marcin Kulisz a écrit : > On 2015-04-29 14:55:48, Emmanuel Kasper wrote: >> Hi List > > Hello, > >> I exchanged some mails mit Jan on the topic of Official vagrant base >> boxes, and we came to the conclusion it would be nice to have our

Re: vagrant lxc images (was "Git repo for debian VM templates")

Hello Antonio > I use vagrant with lxc on a daily bases and have my hacky scripts to > build images: > > http://anonscm.debian.org/cgit/users/terceiro/vagrant-lxc-images.git > > of course you cannot compare sizes of lxc images against virtualbox > ones, but the last jessie image I built was just 78

Re: (more) debian docker images, cloud image optimisations

Hi Jonathan >> However, for executing in a docker/cloud/container environment, some of the >> changes they make do make a lot of sense. E.g. turning off caching, including >> disk caching (unsafe-io), etc.: since the mantra is, if a container fails, >> start a new one. There are other optimisation

Bug#785457: cloud.debian.org: AMI don't need getty

Ognyan, Can you please post a a process list of the getty processes you see in the Amazon hvm ? I am not aware of all the modifications made to the Debian AWS but according to http://0pointer.de/blog/projects/serial-console.html: Two VTs are handled specially by the auto-spawning logic: firstly

Bug#787298: (no subject)

> 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 the best of my knowledge, I would define it as all the packages with Priority: required and important. According to the Debian Jessie instal

Should cloud-init be used only for initial setup of the VM, or left active during the VM lifetime ?

Hi List I am building with the nice folks at Proxmox[1] a virtualization platform, based on Debian, KVM and LXC, with a rest api and a web front end. We are considering adding cloud-init support in our API to add an out-of-VM way of doing the system. As I don't have preliminary experience with clo

Re: Should cloud-init be used only for initial setup of the VM, or left active during the VM lifetime ?

Thanks all for your feedback. We will most probably leave cloud-init running all time. Emmanuel On 06/16/2015 08:33 AM, gustavo panizzo (gfa) wrote: > > > On 2015-06-11 20:58, Emmanuel Kasper wrote: >> Hi List I am building with the nice folks at Proxmox[1] a >> virtualiz

Re: bootstrap-vz configs for vanilla debian boxes: initial commit

Hi Jan Le 16/06/2015 00:04, Jan Niggemann a écrit :> > Zitat von emman...@libera.cc: >> Looking forward to git pull. Did you push your work on Alioth ? > Yep: https://alioth.debian.org/scm/browser.php?group_id=100865 > > It seems you pushed into the git repo used to manage the team's website on

Re: vagrant - debiansid

Le 14/08/2015 14:51, olivier sallou a écrit :> ok, > I found the issue, but this is not resolved. > I remind I tried to create a debian sid. > > The default network interface name created (from recent udev it seems) is > enp0s3, not eth0. In /etc/network/interfaces, there is a declaration for >

Re: Requirements for official Debian images

On 08/24/2015 02:06 PM, Olivier Berger wrote: > Hi. > > Last week at DebConf15, we have discussed with Emmanuel Kasper (glad to > have finally met, btw :-), the issue of official Debian images. :) > I think that Emmanuel has been able to attend the Debian CD BoF (wich I > cou

Re: Requirements for official Debian images

>> Note that I played with the boostrap-vz packaging repo from Marcin > during debconf, and it worked well enough for me to replace using packer > in the future. > > That's very encouraging news Emmanuel. Please do let me know if there is > anything I can be of assistance with. I'm the creator/mai

Re: Requirements for official Debian images

> You might be thinking about > https://lists.debian.org/debian-cloud/2013/04/msg00085.html Thank you Even better I found the wiki article https://wiki.debian.org/Teams/DPL/OfficialImages which summs the discussion you had I will use this is a base for the Vagrant cloud images Manu

New Vagrant base boxes for Debian 7.9 and Debian 8.2

Hello ! I have uploaded Vagrant base boxes for Debian 7.9 and Debian 8.2 to Atlas (VirtualBox provider) cat SHA256SUMS b32c6fa1a29976a10622e9abb44a4707e955d1f18d5517223df4e4b7e068ef39 debian-jessie.box 27103fa1bad281b80400a5d5515541404a07e1728e5868b185f2ff834798caa4 debian-wheezy.box You can star

Re: linux-headers should be installed on the vagrant base boxes

On 09/11/2015 10:56 PM, Joshua Stauter wrote: > Hello all > > I have been working with the images on atlas[0] and a not insignificant > pain point is that whenever you rebuild a box you have to manually go in > (outside of vagrant) and install the appropriate linux-headers-$(uname -r) > package in

Re: linux-headers should be installed on the vagrant base boxes

Hi Josh > >> I think you mean the debian-cloud pseudo package. > > Apologies, I do mean that. However, as you can see[1], there is no result > for that either. Actually *my* apologies ;) The name of the virtual package in the BTS is cloud.debian.org. I fixed that in the box description on atlas

Virtualbox host and guest extensions mismatch and the vagrant debian base box

Le 14/09/2015 16:40, Joshua Stauter a écrit : > My host os is Mac OS X and I have experienced this on both VirtualBox 5 and > later editions of the 4.3 release (installed from homebrew cask > versions[0]). Hi Joshua I just tryed to boot the debian base box with Virtualbox 5.0 and the shared fold

Re: Virtualbox host and guest extensions mismatch and the vagrant debian base box

Hi Joshua > Great insight. I installed that on a whim a long time ago, and completely > forgot about it as I usually use VMware. Welp, I guess I'll fuck off now, > but allow me to ask: any plans for releasing a VMware edition? Whatever the > answer, be assured that your work remains highly appreci

Bug#801056: (no subject)

Hi Guruprasad I had a look at the vagrant-vbguest code, and it looks like it should be able to install the kernel headers by itself. Looking at https://github.com/dotless-de/vagrant-vbguest/blob/master/lib/vagrant-vbguest/installers/debian.rb, I see: def dependencies packages = ['

Bug#801636: Install suite jessie (not wheezy) in jessie image

> Eye-balling the configuration file for building the jessie image I > noticed the "d-i mirror/suite string wheezy". It looked strange to me > so I patched it locally to "jessie" because I thought it made more > sense and I am filing this ticket hoping it is useful. I am not sure > this is a correc

Re: Vagrant kfreebsd base box?

Le 15/10/2015 00:38, Steven Chamberlain a écrit : > Hi Luca, > > Luca Favatella wrote: >> (The idea is that kfreebsd-* Vagrant boxes would help contributions to >> the kfrebsd-* ports by developers hacking on GNU/kFreeBSD only >> intermittently.) > > Yes, it definitely would be useful. Many peop

Re: Vagrant kfreebsd base box?

Le 20/10/2015 10:52, Steven Chamberlain a écrit : > Luca Favatella wrote: >> * Jenkins jobs shall test building each supported box on each commit >> of the repo; > > That would be great. Yes. But we need a server for that, and running on real hardware, as Virtualbox do not run in a nested virtual

Bug#802567: Review box name

Le 21/10/2015 09:27, Luca Favatella a écrit : > Package: cloud.debian.org > Tags: patch > > [Not sure this is the correct way to report this kind of small issues, > please let me know.] > > Running `make stable-test` on master 577ff13 creates debian-jessie.box > but script expects debian-jessie64

Cloud Image Guidelines

Hi I would like to remind the existence of https://wiki.debian.org/Teams/DPL/OfficialImages from 2013, which is a summup from a discussion from this list IIRC. Emmanuel

Re: Debian images on Microsoft Azure cloud

> Currently, both the Openstack images and the image built for Azure are > using extlinux instead of Grub. I think this is mostly due to a personal > preference from Zigo. extlinux works fine but this is a deviation of > what a user would expect of a regular Debian installation. > > Should cloud i

Removing non-free parts of Vagrant Base box creation

Hi List Just to keep you informed, I am going to remove the installation of Virtualbox guest additions ( and therefore shared folder functionnality ) in the vagrant base boxes built for Atlas, because those Cirtualbox additions are contrib/non-free. It was pointed out by debian-cd team: see here

Re: Vagrant box & VirtualBox file sharing

>> Thanks for maintaining the https://atlas.hashicorp.com/debian/boxes/jessie64 >> Vagrant box. >> >> TL;DR: Is there any interest in having this project publish an image that >> does support the vboxsf filesystem? I would be hugely in favor of that. I >> can possibly contribute work toward generat

Virtualbox kernel module

>> Hi Asheesh & Antonio >> First thanks for the interest on these boxes. >> >> After some second thought, I agreee on that. >> I will re enable the vboxfs in the Vagrant Box and move that to a >> "contrib" namespace. >> > > Yay! Thanks so much. > > BTW, one other note: > > The VirtualBox shared

Re: Debian Vagrant Base Boxes

Le 06/01/2016 04:11, Ryan Bantz a écrit : > Hi Emmanuel, > > I noticed that you don't have any base boxes for the VMWare provider. I > utilize Vmware fusion and would like to have one. If I put one together can > we publish it? > > I haven't built a box yet but it looks fairly easy with packer. A

Re: Packer configuration for vagrant with libvirt

Le 02/02/2016 01:00, Martin Vietz a écrit : > Hi guys, Hi Martin > I made a vagrant box with libvirt as provider based on your > debian-vm-templates/packer-virtualbox-vagrant configuration. Maybe > you're interested in this. > > The relevant differences are listed in the attached patch. A workin

Re: [vagrant] official Debian lxc boxes

Le 04/02/2016 17:14, Antonio Terceiro a écrit : > On Thu, Feb 04, 2016 at 12:35:15PM -0200, Tiago Ilieve wrote: >> Hi Antonio, >> >> On 4 February 2016 at 09:48, Antonio Terceiro wrote: >>> That said I noted that we did not have a recent build after v8.1, >>> so I am uploading one just now. >> >>

Re: [vagrant] official Debian lxc boxes

On 02/08/2016 01:34 PM, Antonio Terceiro wrote: > On Sat, Feb 06, 2016 at 01:13:46PM -0200, Tiago Ilieve wrote: >> Emmanuel, >> >> On 5 February 2016 at 16:10, Emmanuel K wrote: > [...] >>> a big point here is that packer with the virtualbox provider requires >>> the build to be run on physical ha

Re: Cloud images on cdimage

On 02/15/2016 01:03 PM, Zied Debian wrote: > Hi Antonio, > >> >> Emmanuel is looking into this. We'll prototype and test the build of >> all the images we want, and then produce patches to the image building >> scripts that build the current images. > > I can help with some steps for these task (

Re: Cloud images on cdimage

Le 17/02/2016 00:08, Zied ABID a écrit : >>> Hi Zied >>> (removind -cd from thread) >>> We don't have a wiki page or paragraph describing how to build and use >>> the LXC Vagrant boxes maybe that would be a good point to start ? >>> Emmanuel >> >> Ok for me, I'll begin with that ;) > > I began a V

Re: Debian Vagrant boxes and Virtualbox

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 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 fold

Re: Building cloud images on Debian infrastructure

Le 30/03/2016 15:13, Riku Voipio a écrit : > On Tue, Mar 29, 2016 at 02:54:51PM +0200, Bastian Blank wrote: >> As already known, Steve, Martin and me talked about how we could build >> Azure and all the other images on Debian infrastructure. The results of >> this meeting were posted by Martin and

Re: Jessie Vagrant/VirtualBox image stuck booting ?

On 04/12/2016 02:27 PM, Olivier Berger wrote: > Hi. > > I've tried to generate a Vagrant box with bootstrap-vz (master branch > latest) which worked. > > However, after vagrant init / vagrant up, the boot doesn't work so well: > the VM boots, but gets stuck at : > Loading Linux 3.16.0-4-amd64

Re: Jessie Vagrant/VirtualBox image stuck booting ?

> > After testing again in order to be able to stop the boot process and > changing the grub config generation code, to set GRUB_TIMEOUT=3 > (unfortunately, this ain't configurable through the manifest and > hardcoded in bootstrapvz/common/tasks/grup.py AFAIU), I've tested with > different kernel

Re: [vagrant] issues with jessie64

Le 23/04/2016 23:25, Martin Zobel-Helas a écrit : > Hi, > > today i tried a vagrant box from https://atlas.hashicorp.com/debian/. > > I have several issues with that box: > > * Why is apt-listchanges installed on that box? That is way away from a > default installation. > * Why does it come wi

Re: [vagrant] issues with jessie64

Le 24/04/2016 17:46, Martin Zobel-Helas a écrit : >> Please don't. I don't know what your use cases are, but nearly every >> time I've used Vagrant, I needed a quick and ready-to-use OS >> installation that could be easily thrown away. Of course some of the >> packages you listed are probably won't

Re: [vagrant] issues with jessie64

Le 25/04/2016 19:19, Emmanuel Kasper a écrit : > Le 24/04/2016 17:46, Martin Zobel-Helas a écrit : >>> Please don't. I don't know what your use cases are, but nearly every >>> time I've used Vagrant, I needed a quick and ready-to-use OS >>> installatio

Re: [vagrant] issues with jessie64

Am 25. April 2016 20:49:12 MESZ, schrieb Martin Zobel-Helas : >Hi, > >On Mon Apr 25, 2016 at 19:47:40 +0200, Emmanuel Kasper wrote: >> Le 25/04/2016 19:19, Emmanuel Kasper a écrit : >> > Le 24/04/2016 17:46, Martin Zobel-Helas a écrit : >> >>> Please don&

Fwd: Debian 8.4 Vagrant Image Error

>while using the Debian 8.4 Vagrant Image I discovered the following: - The 8.4 Image runs well on Virtualbox but the KVM Version fails to start - The 8.4 Image for Virtualbox can be converted to KVM via Vagrant Mutate but fails to start as well Both approaches lead to the same bootloader error

Re: Packer as Debian package

Le 04/05/2016 19:24, Daniel Stender a écrit : > Hi, > > wanted to drop the note that Packer is now available as Debian package: > https://packages.debian.org/unstable/packer > > Thanks, > DS > Hi Daniel Thanks for closing the RFP bug :) I've seen packaging for go is not that trivial due to the

Questions about bootstrap-vz

Hi Anders & Aalii I am looking at boostrap-vz with the aim of solving https://github.com/andsens/bootstrap-vz/issues/247 * After calling python setup.py install from git master, creating my vagrant box fails with IOError: [Errno 2] No such file or directory: '/usr/local/lib/python2.7/dist-packag

Re: Vagrant libvirt mount error rpc.statd

Le 10/06/2016 18:34, Martin Vietz a écrit : > Hi Antonio, > > On 10.06.2016 12:58, Antonio Terceiro wrote: >> When it worked before, was it using NFS, or rsync? See >> https://github.com/vagrant-libvirt/vagrant-libvirt/issues/419 for a >> discussion on an issue where vagrant chooses a synced folde

Re: [vagrant] issues with jessie64

>>> Hi, >>> >>> On Mon Apr 25, 2016 at 19:47:40 +0200, Emmanuel Kasper wrote: >>> >>>> Le 25/04/2016 19:19, Emmanuel Kasper a écrit : >>>> >>>>> Le 24/04/2016 17:46, Martin Zobel-Helas a écrit : >>>>> >&

Re: [vagrant] issues with jessie64

> > IFF we go that way, can we at least make sure that this image does not > pull in pinentry-gtk2? There is no need to pull in libraries for a GTK > environment. Hi This problem was fixed in the 8.5.1 versions of the boxes, by preselecting pinentry-ncurses before isntallting the standard packag

Re: [vagrant] debian/jessie64 v8.5.1 missing lsb-release and ca-certificate packages

On 07/05/2016 10:11 AM, Rick van den Hof wrote: > Hi Emmanuel, > >> Thanks for your interest for the Vagrant boxes. >> >> The packages you mentioned are of priority 'optional', and were only in >> up to now installed becaused of transitive dependecy via 'recommends'. >> See the debian policy for t

Bug#831302: Vagrant box allows root login with insecure default key

On 07/14/2016 03:04 PM, Felix Dreissig wrote: > Package: cloud.debian.org > Severity: normal > Tags: security > > Dear Debian cloud maintainers, > > in the "jessie64" Vagrant box (and presumably the other Vagrant boxes as > well), the insecure Vagrant default SSH key is installed as authorized ke

Re: Comments on live-build, vmdebootstrap, bootstrap-vz, and live-wrapper

Le 16/08/2016 à 17:56, Sam Hartman a écrit : > > Please note the follow-up to the cloud list. Hi Sam Thank your for this very thorough review of image creation tools. You made me google for "object oriented shell programming" ... But ... could you maybe also have a looker at packer ? ( https://

Bug#837992: cloud.debian.org: vagrant libvirt box NFS mount failure on vagrant up

Package: cloud.debian.org Severity: normal The libvirt box has problem with the default shared mode (NFS) A fresh vagrant up from the atlas box brings: mount -o vers=3,udp 192.168.121.1:/home/manu/Projects/vagrenvs/jatlavirtdef /vagrant if command -v /sbin/init && /sbin/init --version | grep ups

Bug#837992: (no subject)

inital bug discussion happpened via email, but we prefer to have this in the BTS, so move the relevant part of the discussions here > I see three possibility fo fix this: > A) switch to NFSv4 by default via a Vagrant configuration option > NFSv4 does not requires the rpc.statd service to run bef

Bug#837992: nfs problem might be related to rpcbind installation in chroot

Le 16/09/2016 à 10:17, Emmanuel Kasper a écrit : > Package: cloud.debian.org > Severity: normal > > The libvirt box has problem with the default shared mode (NFS) > > A fresh vagrant up from the atlas box brings: > > mount -o vers=3,udp > 192.168.121.1:/home/manu/Pro

Bug#837992: Vagrant NFS bug

window, vagrant will start a background rsync process who watchers via inotify the changes to your current dir and push them to the vagrant guest it is only one way sync though but yes NFS works better becaure of the two way sync commit e434330d46f473e9bc6f5888c3bb260afb87f887 Author: Emmanuel Kas

Re: Vagrant debian/jessie64 8.6.0 not bootable any more

Le 21/09/2016 à 15:31, Łukasz Zaremba a écrit : > On 21/09/16 14:58, Marcin Kulisz wrote: >> I think I had something similar. In my case box it self was up but >> vagrant >> couldn't connect to ssh. When I manually connected with just: >> 'ssh -p [port] -i ~/.vagrant.d/insecure_private_key vagrant@

Re: Vagrant debian/jessie64 8.6.0 not bootable any more

Le 21/09/2016 à 21:35, Łukasz Zaremba a écrit : > On 21/09/16 20:54, Emmanuel Kasper wrote: >> can you login in the box via VirtualGui as vagrant user ( pw vagrant ) >> >> then do as root >> >> echo "pre-up sleep 2" >> /etc/network/interfaces >&g

Re: Vagrant debian/jessie64 8.6.0 not bootable any more

On 09/22/2016 11:42 AM, Łukasz Zaremba wrote: > On 22/09/16 06:55, Emmanuel Kasper wrote: >> I retested the box and it's working here >> so it looks like the embedded Virtualbox DHCP server it not found >> >> can you try an alternative Box ( Centos, Ubuntu

Bug#838999: Acknowledgement (Vagrant box inaccessible due to missing network cable (VirtualBox))

On 09/27/2016 04:49 PM, Laurentiu Pancescu wrote: > Control: merge 838936 838999 > thanks > > Apparently already filed, didn't see that before submitting. Could you > please upload fixed images to Atlas? I've revoked on Atlas the problematic box. I plan to upload a fixed box this weeks ( NB: the

Bug#838999: Acknowledgement (Vagrant box inaccessible due to missing network cable (VirtualBox))

Le 27/09/2016 à 17:34, Emmanuel Kasper a écrit : > On 09/27/2016 04:49 PM, Laurentiu Pancescu wrote: >> Control: merge 838936 838999 >> thanks >> >> Apparently already filed, didn't see that before submitting. Could you >> please upload fixed images to

Bug#838999: (no subject)

Łukasz, I am under the impression that the bug comes from VirtualBox 5.1 from my build environment exporting its OVA under a format which is not backwards compatible with 5.0 Can you check if updgrading to Virtualbox 5.1 allows you to use the 8.6.0 box without problems ?

Bug#838999: (no subject)

after reading the virtualbox forums especially https://forums.virtualbox.org/viewtopic.php?f=7&t=78840#p368748 it is clear that the problem is on the virtualbox side Virtualbox 5.1 exports cannot be direclty mported in 5.0

Bug#838999: (no subject)

I've pushed a new box with version 8.6.1 who should fix the bug ( I tested it in a Virtualbox 5.0.* env and the network works properly) @lukasz: since you were the original bug reporter, feel free to close the bug if it works for you too

Re: Build chain for centos7 boxes (oz. imagefactory)

Le 10/10/2016 à 17:50, Laurentiu Pancescu a écrit : > On 07/10/16 13:15, Emmanuel K wrote: >> Ok if I understand you right you start a virt-install command with a >> kickstarter file ( equivalent of a debian preseed for Debian ). >> Then you from the raw/ qcow2 disk image, imagefactory creates the

Re: fai-diskimage, yet another disk image building tool

On 10/18/2016 01:11 PM, Thomas Lange wrote: > I've just released FAI 5.2, the new version of the Fully Automatic > Installation tool set, which now supports creating cloud^Wdisk images ;-) > > It uses the normall FAI process and it's very fast. Using a small set > of packages the image can be crea

Re: Build chain for centos7 boxes (oz. imagefactory)

> setup.py should generate the file Version.py [2], perhaps you have to > run setup.py sdist - I didn't try it. > > [1] https://apps.fedoraproject.org/packages/imagefactory/sources/spec/ > [2] > https://github.com/redhat-imaging/imagefactory/blob/master/setup.py#L53-L55 > >> All of this look inte

Bug#840070: Vagrant libvirt bug

I assume is on the vagrant-libvirt image on atlas. The vagrant-libvirt boxes are made with vmdeboostrap. Most probably the problem here is because vmdebootstrap was run in a stretch host, and used ext4 tools which are newer than the ext4 tools of jessie. So we could rebuild the image on a jessie

Re: Moving vmdebootstrap development discussions so debian-cloud?

Le 29/10/2016 à 18:52, Lars Wirzenius a écrit : > So, what do you think? Good idea? Bad idea? Hi Lars I am not an active user of vmdebootstrap (I prefer the tools who use the debian-installer) but the cross pollinisation is good. I personally favour having different tools to build VM/cloud images

Re: vmdebootstrap plans

> These days golang is the go, excuse the pun and the fact it compiles to a > single executable means the language and extra packages such as jinja2 are > not required. Hi Chris Please not that vmdebootstrap is written in python, not in go. During the debian-cloud meeting we had a talk about packe

import2vbox: import cloud images or any disk image in virtualbox / vmWare

Hi, I needed this for Vagrant but I tought it might be useful for others. https://github.com/EmmanuelKasper/import2vbox Suppose you created a disk image jessie.raw with the tool of your choice, vmdebootstrap \ --size 10G \ --distribution jessie \ --grub \ --arch am

Re: Bug#850790: cloud.debian.org: Distribute Debian cloud images to LXD

Le 14/01/2017 à 12:43, Vincent Ladeuil a écrit : >> Eirik Schwenke writes: > > > On Tue, 10 Jan 2017 03:19:45 -0500 Jeremy Bicha > wrote: > >> Package: cloud.debian.org > >> > >> I have set up LXD to test Ubuntu images. For more info, see Stephane's > >> tutorials from

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 (

Stretch/Testing Vagrant base box with Virtualbox provider available for test

Hi Following the release of Stretch images for AWS by Marcin, I thought it was a good time to release Stretch/Testing images for Vagrant/Virtualbox After installing vagrant, a call to vagrant init debian/testing64 vagrant up vagrant ssh should bring you a login prompt in a fresh stretch system.

Re: Libvirt/LXC Vagrant box for Stretch

Hi Leonard > Stretch recently entered the last phase of the freeze and is just around the > corner. Up until now we use the “official” debian/jessie64 box[1][2] from > Hashicorp’s Atlas but would like to start testing our stuff with Stretch. I > checked out the repository[3] of the build script

Re: Setting hostnames with hostnamectl on AWS AMIs, missing dbus?

On 02/14/2017 12:16 PM, Adam Bolte wrote: > On 14/02/17 21:45, Adam Bolte wrote: >> On 14/02/17 21:30, Marcin Kulisz wrote: >>> On 2017-02-14 14:59:37, paul wrote: There is a case for arguing that having dbus installed by default is not a minimal setup and perhaps not in-line with user ex

Re: Cloud Team blog or ... what?

>> Another thing I've been considering is that we intend the official cloud >> images to be ready and released at the same time as the primary stretch >> announcement. (Well, I intend this anyway, and am assuming that the rest >> of the cloud team has no major objections.) Ideally the release >> an

Re: Cloud Team blog or ... what?

On 02/21/2017 11:39 PM, Steve McIntyre wrote: > On Fri, Feb 17, 2017 at 05:23:16PM +0100, Emmanuel Kasper wrote: >>>> Another thing I've been considering is that we intend the official cloud >>>> images to be ready and released at the same time as the primary str

Stretch cloud images releases

Le 22/02/2017 à 16:13, Antonio Terceiro a écrit : > On Fri, Feb 17, 2017 at 05:23:16PM +0100, Emmanuel Kasper wrote: >>>> Another thing I've been considering is that we intend the official cloud >>>> images to be ready and released at the same time as the primary

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 interest, I attach you a .json file that I adapted from >>> https://anonscm.debian.o

Re: Vagrant 32bit wheezy basebox

Le 24/03/2017 à 16:16, Antoine Beaupré a écrit : > Hi, > > I needed a Wheezy box built in 32-bit (i386) to test a specific > bug. It seems that all official images are built for 64-bit > processors, however: > > https://atlas.hashicorp.com/debian > > Therefore, I copied the `wheezy.json` file to

Re: Vagrant 32bit wheezy basebox

Le 30/03/2017 à 21:22, Antoine Beaupre a écrit : > On 2017-03-24 16:54:41, Emmanuel Kasper wrote: >> looked good to me, so I applied it (but will not provide 32bits build >> for now) > > why not, if i might ask? maybe because lack of time and interest ? :) I do not want

Re: Debian Stretch on GCE

Le 07/03/2017 à 19:03, Zach Marano a écrit : > Hello Debian Cloud, > We have been successfully building Debian Stretch images and having them > pass our own test suite. I was wondering what your guidance is on making a > Stretch image available to end users before the official release. I was > cons

Re: Why don't use virtualbox to build vagrant virtualbox image?

On 04/02/2017 07:59 PM, Todd E Thomas wrote: > Stéphane, you can find Debian (or other popular) boxes at HashiCorp/Atlas > ; > e.g.: > vagrant init debian/jessie64; vagrant up --provider virtualbox > > It looks

Re: Why don't use virtualbox to build vagrant virtualbox image?

>> @stephane: >> VirtualBox is non-DFSG free. It relies the non free compiler OpenWatom >> to buildthe bios. This is why it is not used to create the Boxes, as we >> want to work with a free toolchain. You can look up the details on the >> ITP buck report for openwatcom. >> > > Ok then I need to u

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. Rel

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 assig

Re: Systemd predictive network interface names for Stretch

>> Generally, to the debian-cloud folks, what are your thoughts here for >> Debian cloud images. The possibility that PCI devices can change is always >> on the table and we shouldn't assume it can't happen in any given >> virtualization environment. I can't speak for all cloud providers but boo

Re: Systemd predictive network interface names for Stretch

Le 07/06/2017 à 09:16, kuLa a écrit : > On 2017-06-06 16:56:25, Zach Marano wrote: >> Sounds good to me too- I haven't come to any other conclusions that will >> sanely >> work by default without introducing more complexity in instance >> initialization >> logic (whether that is part of cloud-ini

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

I uploaded a 8.8 contrib image where each VirtualBox is defined as type 82540EM (intel e1000) can you check it if that fixes the problem for you ? the box is available at https://atlas.hashicorp.com/debian/boxes/sandbox/versions/8.8 I did a cycle of 10 vagrant up / vagrant destroy and could not

Bug#863580: (no subject)

I have uploaded a bug with the fix for contrib-jessie64 at https://atlas.hashicorp.com/debian/boxes/contrib-jessie64 keeping the bug open until all boxes are rebuilt and uploaded

Bug#863580: (no subject)

On 06/08/2017 12:46 PM, Emmanuel Kasper wrote: > I have uploaded a bug with the fix for contrib-jessie64 at it was meant a vagrant *box* with the fix

Re: Urgent: Clound images for Stretch announcement

> New plan: publishing a blog post in bits.debian.org about Debian stretch > images for the cloud on Tuesday 20 June. > >>From the Debian Cloud Sprint [1] and the wiki page [2] looks like the > idea of "official images" is still work in progress. So for the > purpose of this blog post I'll conside

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 pr

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 work

  1   2   3   >