Dan Čermák 0aedddd3b3 [systemd] Ensure that podCreateArgs appear last in ExecStartPre= ... When creating a new pod without the `--name` flag, e.g.: `podman pod create foobar` it will get the name `foobar` implicitly and this will be recorded as the in the `podCreateArgs`. Unfortunately, the implicit name only works if it appears as the **last** argument of the startup command. With 6e2e3a78ed we started appending the pod security policy to the startCommand, resulting in the following `ExecStartPre=` line: ``` /usr/bin/podman pod create --infra-conmon-pidfile %t/pod-foobar.pid --pod-id-file %t/pod-foobar.pod-id foobar --exit-policy=stop ``` This fails to launch, as the `pod create` command expects only a single non-flag parameter, but it assumes that `exit-policy=stop` is a second and terminates immediately instead. This fixes https://github.com/containers/podman/issues/15592 Signed-off-by: Dan Čermák <dcermak@suse.com>		2022-09-14 09:37:02 +02:00
..
define	generate systemd: handle --restart	2021-09-07 13:58:11 +02:00
generate	[systemd] Ensure that podCreateArgs appear last in ExecStartPre=	2022-09-14 09:37:02 +02:00
notifyproxy	kube play: support auto updates and rollbacks	2022-09-06 08:56:55 +02:00
activation.go	pkg/systemd: don't require LISTEN_FDNAMES for socket activation	2021-06-24 09:01:39 -06:00
activation_test.go	pkg/systemd: don't require LISTEN_FDNAMES for socket activation	2021-06-24 09:01:39 -06:00
dbus.go	enable gocritic linter	2022-04-26 18:12:22 +02:00