<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - systemd-sysusers: should not log to host journal when bootstrapping a guest (e.g. in a chroot)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88554">88554</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd-sysusers: should not log to host journal when bootstrapping a guest (e.g. in a chroot)
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>a.c.kalker@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>On host Arch Linux x86_64, when I bootstrap a guest using `pacstrap`,
`systemd-sysusers` gets called during the installation of the systemd package
in the chroot used by `pacstrap`.
The user / group setup done by `systemd-sysusers` works fine, except that
messages about user and group creation end up being logged in the host's
journal, which can be confusing (and might trip IDS systems which monitor the
host's journal for signs of suspicious activity).
(Note that during bootstraps like this, certain 'API' directories, such as
`/run`, are bind-mounted into the chroot. I guess that this is how
`systemd-sysusers` running in the chroot manages to send log messages to the
host.)
I see no reason for `systemd-sysusers` to log information like this to the
journal except when run as part of a unit started during a "first boot",
"out-of-box" experience or whatever. When started manually, output of messages
to standard output / standard error should be sufficient.
Please consider implementing a commandline option to specify how and where
`systemd-sysusers` should log its messages.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>