On 2023-02-03T09:19:44 +0100
Valentin Rothberg <vrothberg@redhat.com> wrote:

> Hi Mark,
>
> Thanks for reaching out.
>
> I suggest using `podman generate systemd` to generate a systemd unit.
> There's also a new way of running Podman inside of systemd called Quadlet
> that ships with the just released Podman v4.4.  A blog about that topic is
> in the pipeline.
>
> Given the complexity of running Podman in systemd, `podman generate
> systemd` and Quadlet are the only supported ways.
>
> In your case, I suggest removing `podman pull` from the service.  In
> contrast to `podman pull`, `podman run` won't redundantly pull the image if
> it's already in the local storage.  That will relax the network bottleneck.

Thanks, I'll look into this. The systemd unit shown in my example is
actually already generated from a template (which is then included as
part of the CoreOS ignition file). I assume I won't have to run
"podman generate systemd" on the target machine? Can I run that on my
local development machine and then upload the results to the machine
that will actually run the service?

--
Mark Raynsford | https://www.io7m.com