Re: [atomic-devel] recommended way of running a container

[Brent Baude <bbaude redhat com>]

On Mon, 2019-05-06 at 13:16 +0200, Farkas Levente wrote:
> On 5/2/19 9:20 PM, Brent Baude wrote:
> > On Thu, 2019-05-02 at 16:12 +0200, Farkas Levente wrote:
> > > - Create a systemd service file on the host for the healthcheck,
> > > - Create a systemd timer  file on the host for the healthcheck.
> > > 
> > 
> > Just for the record, healthchecks are optional.  The systemd
> > service
> > and timer files are created automatically for you with podman and
> > are
> > considered to be transient in nature.  That means if the system is
> > rebooted, that timer and service are deleted.  If the container is
> > started again, they are recreated.
> 
> does it means the recommended way to create one systemd service file
> for
> the container and in this service the ExecStart's podman should have
> to
> be a --healthcheck-command parameter (and may be more) and use the
> podman generated transient timer or service for healtcheck?
> 
> and in this case in case of failure who and how will restart the main
> service?
> 

Farkas,

I'm having trouble understanding your question.  The use of systemd to
control a container and the use of systemd to provide health checks are
mutually exclusive.  You do not need to put anything healthcheck
related in your systemd file that controls the container.