add additional vagrant providers

Bug #1585823 reported by Lucy Llewellyn
48
This bug affects 10 people
Affects Status Importance Assigned to Milestone
cloud-images
Won't Fix
Wishlist
Unassigned

Bug Description

Currently the only supported provider for the Vagrant images is Virtualbox. It would be helpful to include additional providers such as Vagrant-Docker, Vagrant-Hyperv, and Vagrant-VMware. My personal use would benefit from the Docker provider being supported.

Dan Watkins (oddbloke)
Changed in cloud-images:
importance: Undecided → Wishlist
Revision history for this message
Emil Madsen (skeen) wrote :

Our company is currently utilizing Debian's Stretch v9.1.0 and Jessie v8.7.0 images, as these provide VirtualBox, Libvirt and LXC images, all of which are needed for us.

With only a VirtualBox image available for Ubuntu, we simply cannot switch over, even though we would like to.

Revision history for this message
Andy Botting (andybotting) wrote :

I was a bit surprised to notice that Ubuntu isn't shipping libvirt images like all the other major vendors. Would be great if you could add these.

Revision history for this message
John Chittum (jchittum) wrote :

the year is 2024, this ticket has been open since 2016, with the last movement in 2017. Canonical and Debian have been reviewing policies around vagrant (the package).

in Ubuntu 24.04, vagrant was removed from the Ubuntu archives. For Ubuntu images, we have treated vagrant images as a developer based experience with community level support. Our ability as a team to support these images has primarily been tied to using vagrant from the archive, and supporting users with matching versions to those vagrant binaries and packaged guest additions. With vagrant being dropped from the archive at this time, we have decided that expansion to new vagrant providers is not feasible.

We have written public documentation on creating Ubuntu vagrant images:
https://documentation.ubuntu.com/public-images/en/latest/public-images-how-to/build-vagrant-with-bartender/

the code will remain in livecd-rootfs, and be open to the community to file bugs if a something is completely broken. we also welcome community contributions to the code and to the documentation.

Changed in cloud-images:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.