So while pid1 survives the EMFILES, udevd does not. Working container:
1058 writev(2, [{"rules contain 49152 bytes tokens (4096 * 12 bytes), 13886
bytes strings", 71}, {"\n", 1}], 2) = 72
[...]
1058 inotify_init1(O_CLOEXEC) = 8
Failing container:
writev(2, [{"rules contain 49152 byte
This is how this can be debugged with lxd: Change the reproducer script
to not delete the "working" containers, but leave them running. Then
booting the failed x-013 (or whichever it is) will fail reliably. "lxc
stop -f x-013" it, then "lxc config edit x-013" and add the following
keys:
config:
Marking as invalid for juju-core as it is reproducible outside of juju
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
Status: In Progress => Invalid
** Changed in: juju-core
Milestone: 2.0-beta12 => None
--
You received this bug no
