Hahahhahaha
So....
yeah....
because the _host_ bootid is in use =) and you didn't reboot the host.
Specifically, everything in systemd reads
/proc/sys/kernel/random/boot_id and that appears to be the same as on
the host.
Maybe lxc/lxd should fake that file and generate new "boot_id" each time
container is started.
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => Invalid
** Changed in: systemd (Ubuntu Eoan)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831258
Title:
journalctl --list-boots does not recognize boots in a container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1831258/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
