Bug #7133: Vagrant cannot build Wheezy-based images from disk

Bug #7133

Vagrant cannot build Wheezy-based images from disk

Added by anonym 2014-04-28 23:14:52 . Updated 2014-09-02 05:17:21 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Build system

Target version:

Tails_1.1.1

Start date:

2014-04-28

Due date:

% Done:

100%

Feature Branch:

feature/vagrant-wheezy-basebox

Type of work:

Code

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

Apparently the current 9 GiBs isn’t enough for the base Debian system, Tails’ Git, apt-cacher-ng’s package cache and the temporary disk space needed for building a Tails based on Wheezy from disk.

To fix this we’ll have to create a new basebox with a larger virtual disk, and users will have to delete their old Vagrant instances.

Note that Vagrant building from RAM is a separate issue that is much easier to solve (~~Bug #7132~~).

Subtasks

Related issues

Blocked by Tails - ~~Bug #7643~~: Vagrant 1.4.3 (from sid) needed on Wheezy

Resolved

2014-07-22

History

#1 Updated by intrigeri 2014-07-09 12:49:01

Parent task set to ~~Feature #7526~~

#2 Updated by intrigeri 2014-07-09 12:51:03

Parent task changed from ~~Feature #7526~~ to ~~Bug #7527~~

#3 Updated by intrigeri 2014-07-09 12:55:09

Assignee set to anonym

#4 Updated by anonym 2014-07-10 21:15:17

Status changed from Confirmed to In Progress
Assignee deleted (~~anonym~~)
Target version set to Tails_1.1
% Done changed from 0 to 50
QA Check set to Ready for QA
Feature Branch set to feature/vagrant-wheezy-basebox

Fixed! A rake build with the branch checked out (or merged into your branch of choice) should now download the new Wheezy-based basebox, provision it, and start a build. Old builder VMs have to be removed manually.

The process of creating new baseboxes has been documented and is more or less a copy-paste or two away.