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

[Farkas Levente <lfarkas lfarkas org>]

yes of course. if kubernetes start the pods then it's not a question.


On 5/3/19 8:41 AM, Scott McCarty wrote:
> I assume by "atomic host" you mean a standalone, non-clustered, aka
> non-Kubernetes environment?
> 
> On Thu, May 2, 2019, 4:12 PM Farkas Levente <lfarkas lfarkas org
> <mailto:lfarkas lfarkas org>> wrote:
> 
>     Hi,
>     I'm just read the blog about healthchecks:
> 
>     https://developers.redhat.com/blog/2019/04/18/monitoring-container-vitality-and-availability-with-podman/
> 
>     What is the current recommended way of running a container on an atomic
>     host using podman? Assume I'd not like to use docker.
>     As I understand it now:
>     - Create a systemd service file on the host for the container,
>     - Create a systemd service file on the host for the healthcheck,
>     - Create a systemd timer  file on the host for the healthcheck.
> 
>     Who should have to restart the container? ie. on the container's service
>     file what is the Restart line and the Type?
> 
>     Is there any recommended template for this?
> 
>     Yes I know there are several ways to do it in container systemd, on host
>     systemd manual healthcheck etc. But IMHO it'd be useful for everybody do
>     give a recommended way or template which is in your planed future way of
>     doing so. AFAIS (after read it) RHEL official container docs is a bit
>     outdated.
> 
>     Thanks in advance.
> 
>     -- 
>       Levente                               "Si vis pacem para bellum!"
> 


-- 
  Levente                               "Si vis pacem para bellum!"