5:36 a.m.
On 06/09/2022 11:56, Daniel Walsh wrote:
On 9/5/22 06:56, lejeczek via Podman wrote:
> Hi guys.
>
> Would you know how, if possible at all, to delay an
> autostart of a container?
>
> My specific scenario is such in which containers-
> auto-started by systemd - reside under a net mount-point
> which is mounted at later stage by ha/pcs(so containers
> fail to start @boot)
> I'd hope that it's doable without extra & "external"
> scripts/tools.
>
> many thanks, L
>
> _______________________________________________
> Podman mailing list --podman(a)lists.podman.io
> To unsubscribe send an email topodman-leave(a)lists.podman.io
Auto started containers in podman are started by the
following unit files at boot time.
/usr/lib/systemd/system/podman-restart.service
/usr/lib/systemd/user/podman-restart.service
Could you make sure that your unit file starts prior to these?
Now, with bit more tampering, I realize that the bit I
"skipped" might be crucial to the question - it is about
rootless containers.
User's home - who owns containers - also resides under the
same mount point (different path).
So what happens when I 'ssh' to the user is:
-> $ ssh appo@localhost
-> $ systemctl --user status -l xyz.service
Unit xyz.service could not be found.
I have to:
-> $ systemctl --user daemon-reload
in order the have 'systemd' pick up such "missing" services
which belong to the user, but!!... that does make 'systemd'
start such container, though now it sees those containers,
containers stay "inactive"
I presume it might be more tricky with 'rootless'
containers, a scenario such as mine.
thanks, L.