From 68511cebe58977ea68ae4f57c6462e979efd1cff Mon Sep 17 00:00:00 2001
From: Michal Sekletar <msekleta@redhat.com>
Date: Tue, 9 Jul 2024 15:21:34 +0200
Subject: coredump: generate properly symbolized stacktrace for containerized
 processes

---
 man/coredump.conf.xml | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

(limited to 'man/coredump.conf.xml')

diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml
index 2eedf942c0..65772d84d7 100644
--- a/man/coredump.conf.xml
+++ b/man/coredump.conf.xml
@@ -109,6 +109,21 @@
         </listitem>
       </varlistentry>
 
+      <varlistentry>
+        <term><varname>AccessContainer=</varname></term>
+
+        <listitem><para>Controls whether <command>systemd-coredump</command> will attempt to use the mount tree of
+        a process that crashed within a container. Access to the container's filesystem might be necessary to generate
+        a fully symbolized backtrace. If set to <literal>yes</literal>, then <command>systemd-coredump</command> will
+        obtain the mount tree from corresponding mount namespace and will try to generate the stack trace using the
+        binary and libraries from the mount namespace. Note that the coredump of the containerized process might
+        still be saved in <filename>/var/lib/systemd/coredump/</filename> even if <varname>AccessContainer=</varname>
+        is set to <literal>no</literal>. Defaults to <literal>no</literal>.</para>
+
+        <xi:include href="version-info.xml" xpointer="v257"/>
+        </listitem>
+      </varlistentry>
+
       <varlistentry>
         <term><varname>ExternalSizeMax=</varname></term>
         <term><varname>JournalSizeMax=</varname></term>
-- 
cgit v1.2.3