thanks of the update. Just in in case anyone else here is interested in a temporary workaround, this is what I did for my use case:
- create a config file for dbus like the one mentioned in comment #2
- apt remove apparmor
- reboot
After that "runlevel", "systemctl is-system-running" and "cloud-init -status --wait" should work.
Last but not least, I would like to mention this issue affects running autopkgtests in nested containers (autopkgtest uses "runlevel" to detect if the container is properly started), I had an interesting conversation about this here (thanks a lot ddstreet for the help!): https://irclogs.ubuntu.com/2022/06/13/%23ubuntu-devel.html#t15:05
Hi there,
thanks of the update. Just in in case anyone else here is interested in a temporary workaround, this is what I did for my use case:
- create a config file for dbus like the one mentioned in comment #2
- apt remove apparmor
- reboot
After that "runlevel", "systemctl is-system-running" and "cloud-init -status --wait" should work.
Last but not least, I would like to mention this issue affects running autopkgtests in nested containers (autopkgtest uses "runlevel" to detect if the container is properly started), I had an interesting conversation about this here (thanks a lot ddstreet for the help!): /irclogs. ubuntu. com/2022/ 06/13/% 23ubuntu- devel.html# t15:05
https:/