[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-06-13 Thread Benjamin Drung
** Changed in: apport Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: systemd-coredump handler does not forward the crash to the container

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-05-06 Thread Benjamin Drung
I requested to standardize forwarding crashes to containers: https://github.com/uapi-group/specifications/issues/102 ** Bug watch added: github.com/uapi-group/specifications/issues #102 https://github.com/uapi-group/specifications/issues/102 -- You received this bug notification because you

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-25 Thread Benjamin Drung
** Changed in: apport Importance: Undecided => Medium ** Changed in: apport Status: New => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-25 Thread Benjamin Drung
Apport cannot do anything useful with these crash reports, because the information about the crashed process does not contain the process number seen from inside the container and because the crashed process is already gone when Apport gets the crash from systemd-coredump. So let Apport just

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Nick Rosbrook
Okay. The title should be changed then -- systemd-coredump on the host attempts to forward the crash to the container, but finds that systemd- coredump is not present in the container, so it falls back to keeping it on the host. -- You received this bug notification because you are a member of

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Ravi Kant Sharma
>Did you verify that systemd-coredump is installed in the container? It works when systemd-coredump is installed inside the container. This report is for the default noble container. My understanding is that in no case should the .crash file be on the host when a crash occurs inside a container.

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Benjamin Drung
Nick, it works if you have systemd-coredump installed in the container. If you do not have systemd-coredump installed in the container, apport on the host should do the forwarding. ** Changed in: apport (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Nick Rosbrook
root@selected-slug:~# machinectl pull-raw "http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; noble Enqueued transfer job 1. Press C-c to continue download in background. Pulling 'http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img', saving

[Bug 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Nick Rosbrook
Did you verify that systemd-coredump is installed in the container? ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063349 Title: