systemd: accept also /sbin/init

it is a regression caused by
3ba3e1c7510d1780b6527a4aa52e40ac2c5b576a.

Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1761514

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
This commit is contained in:
Giuseppe Scrivano
2019-10-15 11:14:19 +02:00
parent a9190dac36
commit 38a6a2000a
3 changed files with 9 additions and 11 deletions

View File

@ -716,12 +716,11 @@ Run container in systemd mode. The default is *true*.
The value *always* enforces the systemd mode is enforced without
looking at the executable name. Otherwise, if set to true and the
command you are running inside the container is systemd or
/usr/sbin/init.
command you are running inside the container is systemd, /usr/sbin/init
or /sbin/init.
If the command you are running inside of the container is systemd or
/usr/sbin/init, Podman will setup tmpfs mount points in the following
directories:
If the command you are running inside of the container is systemd,
Podman will setup tmpfs mount points in the following directories:
/run, /run/lock, /tmp, /sys/fs/cgroup/systemd, /var/lib/journal

View File

@ -753,12 +753,11 @@ Run container in systemd mode. The default is *true*.
The value *always* enforces the systemd mode is enforced without
looking at the executable name. Otherwise, if set to true and the
command you are running inside the container is systemd or
/usr/sbin/init.
command you are running inside the container is systemd, /usr/sbin/init
or /sbin/init.
If the command you are running inside of the container is systemd or
/usr/sbin/init, Podman will setup tmpfs mount points in the following
directories:
If the command you are running inside of the container is systemd
Podman will setup tmpfs mount points in the following directories:
/run, /run/lock, /tmp, /sys/fs/cgroup/systemd, /var/lib/journal