|
|
[[!meta title="Replacing Vagrant?"]]
|
|
|
---
|
|
|
title: Replacing Vagrant?
|
|
|
---
|
|
|
|
|
|
[[!toc levels=2]]
|
|
|
|
|
|
**Main ticket**: [[!tails_ticket 7526]]
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
|
**Main ticket**: tails/tails#7526
|
|
|
|
|
|
Goals of our Vagrant thing
|
|
|
==========================
|
... | ... | @@ -25,7 +30,7 @@ What we have |
|
|
one too. No idea about Ubuntu 14.04 LTS and upcoming 14.10, let
|
|
|
alone other distros or non-Linux OS.
|
|
|
|
|
|
* Our Vagrant setup has many problems: [[!tails_ticket 7527]].
|
|
|
* Our Vagrant setup has many problems: tails/tails#7527.
|
|
|
|
|
|
* What our Vagrant thing does:
|
|
|
- downloads and checks a build basebox as needed
|
... | ... | @@ -84,9 +89,9 @@ Plan |
|
|
====
|
|
|
|
|
|
* Short-term: fix the Vagrant situation for the most important
|
|
|
usecases ([[!tails_ticket 7527]])
|
|
|
usecases (tails/tails#7527)
|
|
|
* Mid-term: fix the situation for real, starting with evaluating
|
|
|
`vagrant-lxc` (in Stretch, [[!tails_ticket 10232]]) and `vagrant-libvirt` (see
|
|
|
[[blueprint|blueprint/vagrant-libvirt]]). If none of those is good
|
|
|
enough, then let's give another look to Docker ([[!tails_ticket
|
|
|
7530]], [[blueprint/evaluate_Docker]]). |
|
|
`vagrant-lxc` (in Stretch, tails/tails#10232) and `vagrant-libvirt` (see
|
|
|
[blueprint](vagrant-libvirt)). If none of those is good
|
|
|
enough, then let's give another look to Docker (tails/tails#7530, [evaluate Docker](evaluate_Docker)).
|
|
|
|