On Tue, Feb 05, 2019 at 06:36:48AM +0530, Prasanna V. Loganathar wrote:
> Hi Stephane,
>
> Thanks for the reply. Please correct me if I'm wrong.
>
> lxc launch ubuntu:18:04 testbox
> lxc exec testbox bash
> sleep 100 & kill -ABRT $(pgrep sleep)
stgraber@castiana:~$ lxc launch ubuntu:18.04 testbo
Hi Stephane,
Ah. I had overlooked this one. It does work well in lxc. Thanks for
pointing that out.
However, apport's default is to do nothing in containers.
docker run --name testbox --rm -it ubuntu bash
> sleep 10 & kill -ABRT $(pgrep sleep)
This has no /var/crash directory. There are no dumps
On Wed, Feb 06, 2019 at 03:05:20AM +0530, Prasanna V. Loganathar wrote:
> Hi Stephane,
>
> Ah. I had overlooked this one. It does work well in lxc. Thanks for
> pointing that out.
> However, apport's default is to do nothing in containers.
>
> docker run --name testbox --rm -it ubuntu bash
> > sl
>
> You need to have apport itself installed in the container, I suspect
> that the Docker containers do not have it.
This will make no difference. Doing an `apt update && apt install -y
apport` will not do any good, as apport is set to disable itself on
containers.
> Having the dump handled by
On Wed, Feb 06, 2019 at 03:35:23AM +0530, Prasanna V. Loganathar wrote:
> >
> > You need to have apport itself installed in the container, I suspect
> > that the Docker containers do not have it.
>
>
> This will make no difference. Doing an `apt update && apt install -y
> apport` will not do any
>
> Except for the part where a coredump for an unknown binary is useless.
If I have a service that crashes in a container. I'd like to get back into
the container and inspect why. Simply throwing out unknown binary crashes
doesn't exactly seem like a stellar decision to me. And unknown binary to
>
> So having all the dumps centralized on the host when you don't know what
> container it came from and may no longer have any of the environment
> information is completely useless.
>
Adding on to my previous reply, perhaps there's a misunderstanding on this
one? Who's forwarding dumps to the h
On Wed, Feb 06, 2019 at 04:57:32AM +0530, Prasanna V. Loganathar wrote:
> >
> > So having all the dumps centralized on the host when you don't know what
> > container it came from and may no longer have any of the environment
> > information is completely useless.
> >
>
> Adding on to my previous
Hi Stephane,
Thanks for the reply. Please correct me if I'm wrong.
lxc launch ubuntu:18:04 testbox
lxc exec testbox bash
sleep 100 & kill -ABRT $(pgrep sleep)
There's no crash dump anywhere.
/var/crash is empty. No `core` file, etc. The default is
crashes just vaporises itself - that's my bigge
>
> Nope, everything landing through the helper on the host is what happens
> whenever you have a core pattern that starts with a "|". Similarly, any
> pattern which isn't just a file name (like "core") but is instead an
> absolute path, will be treated as an absolute path on the host, not in
> the
10 matches
Mail list logo
