I put some scripts I've been using to test things here https://github.com/mwhudson/livefs-disaster-debugging for now.
Thanks to a suggestion from Nick, it seems that https://code.launchpad.net/~mwhudson/launchpad-buildd/+git/launchpad- buildd/+merge/499051 will mean that focal and newer images work with cgroupsv2 (needs more testing but that's what local play suggests). If this pans out I would suggest that the way forward is to land this and change the builder VMs to boot with cgroupsv2. This should let resolute builds work again but I expect it will break xenial and perhaps bionic builds, which seems a better place than where we are now. To get xenial and (maybe) bionic builds going again, we might be able to allocate one builder that boots with cgroupsv1 and direct the small number of builds for that series to that builder. I'm not sure how that would work but Guruprasad said it might be possible :-) In the longer term it would be good to move away from privileged containers as they are becoming less and less supported by other parts of the ecosystem. I've been playing around trying to run builds in an unprivileged container and I think we can probably make this work but the hacks required might be a little terrifying (the repo above contains my scripts for this as well). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2138708 Title: livefs builders unable to build images for Resolute To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/2138708/+subscriptions -- kubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
