I think the consensus at this point is that, while this manifests in LXD
(and chroot), it's ultimately a kernel configuration issue. Marking lxd
invalid.
Just to fill in a bit of background, there's been some discussion
between kernel team and foundations what the correct course of action
here is and I think the consensus is "just flip COMPAT_32BIT_TIME back
on". The one remaining question, looking at the original bug that
flipped that switch in the first place (LP: #2038582) is: should this
change be limited to linux-raspi?
** Changed in: lxd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
Title:
Cannot launch armhf containers on arm64 host under noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/2062176/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
