Hallo Daniels, thanks for the advice. I tried to run the pod using quadlet,
but I hit the same problem. It seems that when started under quadlet all
containers, belonging to the pod are started up without checking whether
the other containers are already in healthy state or not.
Is there a way to specify container dependencies inside podman/kubernetes pod?
I don't like to run oracle in a separate container and define dependencies
using systemd After/Require options. I prefer to keep oracle container in
single pod with application, so that it is not necessary to map oracle port
to different value for each application.
Best regards,
--
Michael Ivanov
On 21.11.2023 17:39, Daniel Walsh
wrote:
On 11/21/23 09:33, Михаил Иванов
wrote:
Hallo Valentin, the actual case is to wait until oracle container
is in healthy state and only then allow to access it from the other
container. Currently I loop on oracle container health check before
running the second container. This approach is possible when I run
containers from shell script, but probably will not work in eg. kubernetes.
Rgrds,
This sounds exactly like a systemd use case, have you investigated
using quadlet for this?
On 21.11.2023 11:49, Valentin
Rothberg wrote:
Thanks for reaching out, Michael.
Hi, is it possible to run health check on a container from another container in same pod?
The answer is probably no, but I want to make sure to
understand your use case. Can you elaborate on it in
more detail?
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io
_______________________________________________
Podman mailing list -- podman@lists.podman.io
To unsubscribe send an email to podman-leave@lists.podman.io