Vagrant: LXD provider

Created on 7 May 2016 · 7Comments · Source: hashicorp/vagrant

Vagrant version

1.8.1

Host operating system

Linux.

Guest operating system

Linux.

Expected behavior

What should have happened?

Create lightweight LXD container.

Actual behavior

What actually happened?

Don't know how to do that with Vagrant.

Steps to reproduce

Open https://www.vagrantup.com/docs/providers/
Try to find available plugins (vagrant list doesn't work for remotes)
Get frustrated

References

https://github.com/lxc/lxd

Source

techtonik

👍4

Most helpful comment

The sources can be found here:
https://github.com/georghopp/vagrant-lxd

ghost on 20 May 2017

👍6

All 7 comments

Hi @techtonik

Thank you for opening an issue. With regard to new providers and features, we generally prefer to see these types of things implemented as plugins before building them into Vagrant core directly (see vagrant-aws, vagrant-digitalocean, vagrant-parallels, for examples). Thanks!

sethvargo on 7 May 2016

👍1

https://github.com/mitchellh/vagrant/wiki/Available-Vagrant-Plugins

techtonik on 11 May 2016

Hi,
I know this is dead and buried but google still brings this up pretty early when you search for vagrant and lxd, so I add a post here to announce that I have written a provider plugin for lxd.
It is still pretty alpha, but does what I needed. Maybe this is of some help.
It is available via rubygems, so vagrant plugin install vagrant-lxd works. The source as well as some example boxes can be found here on github. These example boxes are also available on atlas. You may search for boxes from user ghopp.
Best regards,
Georg

ghost on 20 May 2017

@georghopp better post a link to those sources and the next time somebody tries to find it, Google may sent to the correct page.

techtonik on 20 May 2017

The sources can be found here:
https://github.com/georghopp/vagrant-lxd

ghost on 20 May 2017

👍6

There's now a plugin developed by Catalyst:

https://gitlab.com/catalyst-it/vagrant-lxd

candeira on 26 Sep 2018

👍3

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.