4 Commits

Author	SHA1	Message	Date
Danila Kiver	2bfade4391	Do not hardcode podman binary location in generate systemd. ... It is not correct to rely on specific location of the podman binary. In most cases it is /usr/bin/podman, but sometimes is not (e.g. in system tests). Use /proc/self/exe instead of hardcoded path. Signed-off-by: Danila Kiver <danila.kiver@mail.ru>	2019-07-07 11:20:41 +03:00
Danila Kiver	a54429cf87	Use conmon pidfile in generated systemd unit as PIDFile. ... By default, podman points PIDFile in generated unit file to non-existent location. As a result, the unit file, generated by podman, is broken: an attempt to start this unit without prior modification results in a crash, because systemd can not find the pidfile of service's main process. Fix the value of "PIDFile" and add a system test for this case. Signed-off-by: Danila Kiver <danila.kiver@mail.ru>	2019-07-04 03:58:37 +03:00
baude	faf499cf94	add unit tests for generate systemd ... it looks like i forgot to add the unit tests for generate systemd Signed-off-by: baude <bbaude@redhat.com>	2019-05-06 09:14:10 -05:00
baude	c18ad2bfd9	Generate systemd unit files for containers ... the podman generate systemd command will generate a systemd unit file based on the attributes of an existing container and user inputs. the command outputs the unit file to stdout for the user to copy or redirect. it is enabled for the remote client as well. users can set a restart policy as well as define a stop timeout override for the container. Signed-off-by: baude <bbaude@redhat.com>	2019-05-02 14:35:53 -05:00