| Thread Previous • Date Previous • Date Next • Thread Next |
** No longer affects: sbuild-launchpad-chroot (Ubuntu Xenial)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1652117
Title:
sbuild-launchpad-chroot doesn't detect current overlayfs
Status in sbuild-launchpad-chroot package in Ubuntu:
Triaged
Status in sbuild-launchpad-chroot source package in Yakkety:
Triaged
Status in sbuild-launchpad-chroot source package in Zesty:
Triaged
Bug description:
With the switch from out of tree overlayfs to in-tree overlay, sbuild-
launchpad-chroot must be updated to properly detect both of those,
otherwise users end up with a "directory" type chroot that doesn't use
unioning and so looses a few of the useful features provided by this
tool.
# Rationale
New kernel doesn't have a "overlayfs" module, it's now called "overlay".
Both names should be used in the detection code.
# Test case
- Before upgrade
- sbuild-launchpad-chroot create -n test -s xenial -a amd64
- Check that /etc/schroot/chroot.d/test doesn't contain "union-type"
- sbuild-launchpad-chroot remove -n test
- After upgrade
- sbuild-launchpad-chroot create -n test -s xenial -a amd64
- Check that /etc/schroot/chroot.d/test contains "union-type"
- sbuild-launchpad-chroot remove -n test
# Regression potential
Not much, this won't affect anyone who has existing chroots, it only affects new chroots and re-introduces the behavior that people have been expecting up until the time where the overlayfs driver was removed from the kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1652117/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
