Lennart Poettering on Nostr: …logged events it all stopped on the container boundary: only with luck you'd get a ...
…logged events it all stopped on the container boundary: only with luck you'd get a proper back trace, but you usually didn't because the coredump processor on the host couldn't deal with the different compiler/debug situation inside the container. Given that containers are mildly successful these days this of course is a big problem.
Back in v255 we added a new unit file setting CoredumpReceive= to unit files (services and scopes in particular), to address this issue.
Published at
2024-12-13 09:01:45Event JSON
{
"id": "3c28edebe237f86a289dc87d67dc32fd730254b444350339f407df11b67f3704",
"pubkey": "1d95c32d9a9d95a54f98eb2eaa156f3d3a71dc49eca2c960b2b89962758f1cc0",
"created_at": 1734080505,
"kind": 1,
"tags": [
[
"e",
"879ca42261abe5256fac0b4101b91755a040036401f4c684606dd369f7d5bedc",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/pid_eins/statuses/113644699981447995",
"activitypub"
]
],
"content": "…logged events it all stopped on the container boundary: only with luck you'd get a proper back trace, but you usually didn't because the coredump processor on the host couldn't deal with the different compiler/debug situation inside the container. Given that containers are mildly successful these days this of course is a big problem.\n\nBack in v255 we added a new unit file setting CoredumpReceive= to unit files (services and scopes in particular), to address this issue.",
"sig": "b78c0a7aa3a02926d2aaf02c4725435731b1bffff4d3d9c7ee19a3d6313fc786071c544910766cd3aa8fb376aa3400ec60de0f3ca7ca37f4dd6c2ac6f7a21893"
}
