** Changed in: lxc (Ubuntu)
Status: Confirmed => Invalid
** Changed in: upstart (Ubuntu)
Status: New => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Quoting Shimin (shi...@databricks.com):
> Thanks for looking into it. Are there any downsides to disabling udev in
> the container (by removing /etc/init/udev.conf for example) if we don't
> need the container to be notified of new devices?
hi, no this should have no downsides. You can just
echo
Thanks for looking into it. Are there any downsides to disabling udev in
the container (by removing /etc/init/udev.conf for example) if we don't
need the container to be notified of new devices?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I'm seeing a direct correlation here between the symptom and the kernel
emitting uevents. For example, in the host run:
$ udevadm --monitor
And in another terminal in the host run:
# losetup /dev/loop0 foo
This causes the symptoms even though it has no direct impact on the
container, but does
An strace of the attach shows:
15047 read(0,
15047 +++ killed by SIGKILL +++
15033 <... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGKILL}], 0,
NULL) = 15047
15033 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=15047,
si_uid=0, si_status=SIGKILL, si_utime=2, si_stime=1} ---
(Where the last prompt comes from the lxc-attach having been killed)
stopping lxcfs on the host prevents this from happening.
I don't think lxcfs is to blame, though but rather fuse.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificat
6 matches
Mail list logo
