This bug was fixed in the package lxc - 1:4.0.0-0ubuntu2
---
lxc (1:4.0.0-0ubuntu2) focal; urgency=medium
* Cherry-pick upstream bugfixes:
- 0036-fix-non-root-user-cannot-write-dev-stdout.patch
- 0037-cgroups-fix-uninitialized-transient_len-warning.patch
-
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Invalid
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Invalid
** Changed in: lxc (Ubuntu Bionic)
Status: New => Incomplete
Fix here:
https://github.com/lxc/lxc/pull/3034
** Changed in: lxd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: lxd (Ubuntu Eoan)
Status: New => In Progress
** Changed in: systemd (Ubuntu Bionic)
Status: Invalid => In Progress
** Changed in: systemd (Ubuntu
Filed issue with lxcfs at
https://github.com/lxc/lxcfs/issues/285
** Bug watch added: LXCFS bug tracker #285
https://github.com/lxc/lxcfs/issues/285
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Several people tried to namespace this but this is really tied to a
physical machine so it's kinda tricky to fake.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1831258
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
6 matches
Mail list logo
