vmbuilder ignores host specific settings when existing chroot is used
Bug #592252 reported by
Gunnar Thielebein
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| VMBuilder |
New
|
Undecided
|
Unassigned | ||
Bug Description
When a chroot is created manually via
$debootstrap hardy hardy-chroot
and is referenced in vmbuilder via --existing-chroot switch this ignores all other settings that are host specific like hostname, users, mirror, components.
It is not possible this way to use a precreated chroot for the case of creating individual machines without further amendment.
Related branches
lp:~r.kintzi/vmbuilder/existing-chroot
- Serge Hallyn: Approve
-
Diff: 52 lines (+9/-1)2 files modifiedVMBuilder/contrib/cli.py (+8/-0)
VMBuilder/plugins/ubuntu/distro.py (+1/-1)
To post a comment you must log in.
