Cannot start bash session for buildd vm images in LXD vm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Incomplete
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Ubuntu "bootable" buildd vm images, if imported into lxd and booted in a VM container, cannot produce an interactive bash session via, e.g. `lxd exec <name> bash`.
This appears to be a problem of the buildd image lacking grub settings to produce console output on ttyS0. Lack of console output also prevents the required manual install of the lxd agent as detailed in this [1] Discourse post about booting Ubuntu in lxd vms.
[Impact]
* This negatively impacts the user experience of Ubuntu buildd images in lxd, which is one of the target environments for the buildd images
[Test Case]
* create a metadata.yaml file for the buildd image (these will soon be downloadable from cloud-images.
{
"architecture": "x86_64",
"creation_
"properties": {
"os": "Ubuntu",
"series": "focal"
}
}
* tar the metadata.yaml file into <name>.tar.xz
* obtain the focal buildd image of your choice, e.g. from [2]
* import the image into lxd: `lxd image import <name>.tar.xz <buildd-image>.img`
* follow the "extra steps for official Ubuntu images" in [1] to init, configure, and start a lxd vm using the image by its fingerprint
* Attempt console log in via `lxc console <vm name>` or a bash session via `lxc exec <vm name> bash`
* Note that without console output it is not possible to log in via the lxc console to install the lxd agent, and therefore not possible to obtain a bash session via lxc exec
[Where problems could occur]
* Turning on console output requires changing grub configs; certain values of these configs could break current expectations about buildd image behavior
[Other Info]
* This issue affects buildd images from all suites, but the lxd-agent-loader package is only available for focal+
[1] https:/
[2] http://
Related branches
- Gauthier Jolly (community): Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 57 lines (+20/-0) (has conflicts)3 files modifiedCOPYING (+1/-0)
debian/changelog (+9/-0)
live-build/buildd/hooks/02-disk-image-uefi.binary (+10/-0)
- Steve Langasek: Approve
- Thomas Bechtold (community): Approve
-
Diff: 36 lines (+17/-0)2 files modifieddebian/changelog (+7/-0)
live-build/buildd/hooks/02-disk-image-uefi.binary (+10/-0)
- Steve Langasek: Approve
- Thomas Bechtold (community): Approve
-
Diff: 51 lines (+20/-1)3 files modifieddebian/changelog (+8/-0)
live-build/buildd/hooks/02-disk-image-uefi.binary (+10/-0)
live-build/buildd/hooks/52-linux-virtual-image.binary (+2/-1)
- Steve Langasek: Approve
- Thomas Bechtold (community): Approve
-
Diff: 51 lines (+20/-1)3 files modifieddebian/changelog (+8/-0)
live-build/buildd/hooks/02-disk-image-uefi.binary (+10/-0)
live-build/buildd/hooks/52-linux-virtual-image.binary (+2/-1)
- Robert C Jennings (community): Approve
- Ubuntu Core Development Team: Pending requested
-
Diff: 51 lines (+20/-1)3 files modifieddebian/changelog (+8/-0)
live-build/buildd/hooks/02-disk-image-uefi.binary (+10/-0)
live-build/buildd/hooks/52-linux-virtual-image.binary (+2/-1)
Changed in livecd-rootfs (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in livecd-rootfs (Ubuntu Focal): | |
status: | New → In Progress |
This bug was fixed in the package livecd-rootfs - 2.713
---------------
livecd-rootfs (2.713) hirsute; urgency=medium
* Use the full name of the 'boot' flag in parted calls as it's not good
practice to rely on the shortened, ambiguous version.
-- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 24 Feb 2021 12:55:37 +0100