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

2019-05-07 Thread Brent Baude
On Tue, 2019-05-07 at 13:33 +0200, Farkas Levente wrote: > On 5/6/19 4:11 PM, Brent Baude wrote: > > 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 ser

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

2019-05-07 Thread Farkas Levente
On 5/6/19 4:11 PM, Brent Baude wrote: > 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

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

2019-05-06 Thread Brent Baude
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.

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

2019-05-06 Thread Muayyad AlSadi
there were two ways I used to do this with docker and it can also be done with podman 1. stateless way, always fresh ExecStartPre=-/bin/podman stop -t=1 mycnt ExecStartPre=-/bin/podman remove mycnt ExecStart=/bin/podman run -i --name mycnt -v myimg mycmd ExecReload=-/bin/podman restart -t=1

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

2019-05-06 Thread Farkas Levente
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 system

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

2019-05-03 Thread Farkas Levente
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 > wrote:

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

2019-05-02 Thread Scott McCarty
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 wrote: > Hi, > I'm just read the blog about healthchecks: > > > https://developers.redhat.com/blog/2019/04/18/monitoring-container-vitality-and-availability

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

2019-05-02 Thread Brent Baude
On Thu, 2019-05-02 at 16:12 +0200, 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 >

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

2019-05-02 Thread Daniel Walsh
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?