[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] recommended way of running a container
- From: Daniel Walsh <dwalsh redhat com>
- To: atomic-devel projectatomic io, Brent Baude <bbaude redhat com>
- Subject: Re: [atomic-devel] recommended way of running a container
- Date: Thu, 2 May 2019 14:37:34 -0400
On 5/2/19 10:12 AM, Farkas Levente 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.
>
Brent could you answer this?
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]