Re: Bug#1049999: vagrant: the future of packaging vagrant in Debian

[Lucas Nussbaum <lucas@debian.org>]

Hi,

An update on this:

I plan to take care of the Debian vagrant package (in the framework of
the Ruby team, as this is currently done). I uploaded the latest free
version of Vagrant to unstable/testing
(2.3.7+git20230731.5fc64cde+dfsg-2).

Of course help is welcomed. An easy and useful entry point is to look at
existing bugs, try to reproduce them with the latest version, and report
back.


I do not plan to package the non-free versions of Vagrant.


I also plan to continue to take care of the Debian Vagrant images,
including ensure that they work with the version of Vagrant in Debian.


I also looked a bit at potential alternatives. A project with a good
potential is Incus (a LXD fork by the original LXC/LXD main developer).
It is easy to install, and it provides both VMs and containers support.

However currently it does not provide an equivalent to a Vagrantfile (to
describe the infrastructure to create, what to execute on nodes, etc.).
There's a terraform/opentofu provider, but that doesn't sounds very
exciting regarding complexity. I raised that topic in
https://discuss.linuxcontainers.org/t/incus-as-a-vagrant-replacement/19586
but the discussion did not go anywhere interesting.

Maybe a third party project could create an incus frontend that provides
a Vagrantfile-like interface. Given infinite free time, I would likely
work on that. :)

Lucas