[Bug 2115536] [NEW] [SRU] Allow building WSL images of Focal in the new format
Carlos Nihelton
2115536 at bugs.launchpad.net
Fri Jun 27 21:00:06 UTC 2025
Public bug reported:
[ Impact ]
* Previously, WSL instances relied on a very lightweight build pipeline which was using the CPC image.
In 22.04 we did a first step to have WSL has its own project in livecd-rootfs, with its own seed and image to produce a rootfs, while leaving Focal for later.
* Later, changes to livecd-rootfs and related packages for Noble and
later were implemented to adapt the images to the new format promoted by
WSL that allows distributions to no longer rely on MS Store, which is
becoming deprecated for WSL. Those changes are in the process of being
backported to Jammy.
* Focal is the only LTS still supported via Ubuntu Pro that lacks those
image building capabilities.
* This Stable Release Update request aims to bring Focal to the current state of the art build pipeline of WSL images, allowing us to host the final artifacts in Canonical's infrastructure and no longer depend on MS Store.
* We thus need to promote 'ubuntu-wsl' as its own project in 'livecd-rootfs' for focal, implement the same image building hooks already existing in Jammy and later and create a seed for Focal, which implies in changes to 'ubuntu-meta'.
[ Test Plan ]
* WIP
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the
change is wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the event
of a regression.
* This must never be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* As already explained in LP #2115426, despite Focal being out of
standard support, we need to align its build pipeline to the current
state of the art (implemented for Jammy and later), as MS Store is being
deprecated.
* All the changes in the packages tracked by this SRU bug are related
to each other and need to land together otherwise building a WSl image
of Focal would fail.
* This report relates to LP #2080223 and LP #2091293, but the changes
needed for 20.04 are more complex (as already mentioned in the former),
thus I'd rather do it in a dedicated SRU.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2115536
Title:
[SRU] Allow building WSL images of Focal in the new format
Status in livecd-rootfs package in Ubuntu:
New
Bug description:
[ Impact ]
* Previously, WSL instances relied on a very lightweight build pipeline which was using the CPC image.
In 22.04 we did a first step to have WSL has its own project in livecd-rootfs, with its own seed and image to produce a rootfs, while leaving Focal for later.
* Later, changes to livecd-rootfs and related packages for Noble and
later were implemented to adapt the images to the new format promoted
by WSL that allows distributions to no longer rely on MS Store, which
is becoming deprecated for WSL. Those changes are in the process of
being backported to Jammy.
* Focal is the only LTS still supported via Ubuntu Pro that lacks
those image building capabilities.
* This Stable Release Update request aims to bring Focal to the current state of the art build pipeline of WSL images, allowing us to host the final artifacts in Canonical's infrastructure and no longer depend on MS Store.
* We thus need to promote 'ubuntu-wsl' as its own project in 'livecd-rootfs' for focal, implement the same image building hooks already existing in Jammy and later and create a seed for Focal, which implies in changes to 'ubuntu-meta'.
[ Test Plan ]
* WIP
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the
change is wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the event
of a regression.
* This must never be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* As already explained in LP #2115426, despite Focal being out of
standard support, we need to align its build pipeline to the current
state of the art (implemented for Jammy and later), as MS Store is
being deprecated.
* All the changes in the packages tracked by this SRU bug are related
to each other and need to land together otherwise building a WSl image
of Focal would fail.
* This report relates to LP #2080223 and LP #2091293, but the changes
needed for 20.04 are more complex (as already mentioned in the
former), thus I'd rather do it in a dedicated SRU.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2115536/+subscriptions
More information about the foundations-bugs
mailing list