Dear lovely vagrant box makers,

I noticed that there are no Trixie boxes listed at

https://portal.cloud.hashicorp.com/vagrant/discover/debian
https://app.vagrantup.com/debian (its cooler alias, for now I guess)

Now that Trixie is out, please can a Vagrant box be added for it? I'm an
amd64+libvirt kind of guy myself, but I realise there are more types of box
to pack than just this, and it's a ton of work. Thanks in advance.

I guess this is also a call for debian/testing64 to be bumped so it's
noticably on the Forky path.


    cheers,
    Andrew Chadwick

I don't have the reference to it at hand, but it was announced that
due to the license change of Vagrant all previous contributors lost
interest.

Thus I'd suggest not expecting any further updates to these images.

Best,
Chris

Hi,

I was doing the work required to update Debian images for Vagrant, and
was also involved in the maintenance of the Vagrant package.
The current situation is:

1/ The Vagrant software is now non-free. There's still a package in
Debian (trixie), with the latest free version. There are been discussion
in https://bugs.debian.org/1049999 and in the thread starting with
https://lists.debian.org/debian-release/2025/06/msg00484.html about the
future of this package. Hans-Christoph Steiner is maintaining it at the
moment (even if this doesn't reflect in the Uploaders field of the
package in trixie).

2/ The Vagrant images moved from VagrantCloud to HashiCorp Cloud
Platform. Since then, I frequently ran into issues when uploading new
images, and it's not clear if HashiCorp is going to continue to support
old Vagrant versions with HCP. After contacting HCP's support
about one of those issues (see
https://github.com/hashicorp/vagrant/issues/13571, reported January
10th, fixed March 5th), HashiCorp support replied "you need to update
the Vagrant version if you want to use HCP Vagrant boxes.". It's not
clear if this is an official HashiCorp statement (someone else said they
want to maintain backward compatibility with older versions in the
github issue), but I would not bet on being able to use HCP images
with the free Vagrant version for too long. There was more discussion in
https://bugs.debian.org/1104105.

As a result, I decided to stop maintaining Debian images for Vagrant.
Your options are:

A/ use the latest debian/testing64 image, which was updated on
2025-04-26, so it might be sufficiently close to what Debian trixie
looks like.

B/ find a new maintainer for the Debian images. If someone wants to take
over, the tooling at
https://salsa.debian.org/cloud-team/debian-vagrant-images/ still works
(except maybe for the upload part) and I can walk you through it if
needed.

C/ switch to something else. Personnally, I switched to Incus and since
I missed a declarative way to describe my environments, I wrote Incant,
a Vagrant-inspired frontend that brings that to Incus (see
https://github.com/lnussbaum/incant/).  It's still rough around the
edges but has met my needs, and I heard positive feedback from others.
And I have a few pending changes are MRs to look at, so it will likely
improve soon. Also Incus has an image for Debian trixie uploaded on a
regular basis (daily I think) and usually also has an image for Debian
testing.

Lucas

Hey Lucas,

I would like to maintain Debian images here, e.g. option B).  I requested access
to the project on salsa,
https://salsa.debian.org/cloud-team/debian-vagrant-images/  My handle there is
@eighthave which matches my debian email eighthave@debian.org.  These are all
visible on my GPG key, which is used for Debian as well:

EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556

Hi Hans-Christoph,

I granted you access to the salsa project.

Once you are comfortable with generating images, we also need to grant
you access to the HashiCorp Cloud Platform 'debian' organization (where
the official images are now published).

Please create an account there, and then we (Antonio Terceiro or myself)
can give you access. I think that for some reason creating an account
with my Debian address failed, and I had to use another address. You
might run into the same thing.

Lucas

Lucas Nussbaum:
 > I granted you access to the salsa project.
Thanks!

 > Once you are comfortable with generating images, we also need to grant
 > you access to the HashiCorp Cloud Platform 'debian' organization (where
 > the official images are now published).
I've actually been using this project to generate images for years, since the
old official F-Droid image was just a slight modification of this project.  I
haven't published in two years since F-Droid switched to the official Debian
images, so if there is anything new in the past two years, I'll have to learn it.

 > Please create an account there, and then we (Antonio Terceiro or myself)
 > can give you access. I think that for some reason creating an account
 > with my Debian address failed, and I had to use another address. You
 > might run into the same thing.
Ok, I just created a new account since the old one seems to be defunct now.
That account is eighthave / hans@guardianproject.info (you can find my emails in
my Debian GPG key).

.hc

Hi,

I invited you as an Admin in the debian org on HCP.

Lucas

Lucas Nussbaum:
I accepted.

My plan is to maintain debian/trixie64 boxes for libvirt.  I would consider
updating the debian/bookworm64/libvirt box if there is a request.  I'm no longer
set up on Vagrant since it is not in Debian anymore.  I would be open to someone
else maintaining the Vagrant boxes.

Is there any need for this from the libvirt perspective?  The nocloud
images already published to cloud.debian.org are fully supported for
libvirt.

Unless I'm missing something, the only thing in need of a new maintainer
is the Vagrant stuff specifically.

noah

Noah Meyerhans:

Vagrant boxes are specified per-VM tech, e.g. libvirt, VirtualBox, lxc, etc.  I
mean I will maintain the Vagrant libvirt boxes, but not VirtualBox, lxc, etc.  I
think this is totally separate from the nocloud images.

That said, does anyone know how to use the nocloud image as a Vagrant/libvirt box?

https://salsa.debian.org/cloud-team/debian-vagrant-images/

Could I be granted that?

I posted an official debian/trixie64 release up on vagrantup.com

Hi,

I upgraded you to maintainer. I see that membership is normally handled
through the cloud team's membership, but that you are a direct member
for that project. You would need to talk to the cloud team owners if you
need to be made owner of that project.

Lucas