Feature request description

Kubernetes 1.28 added the formal concept of "sidecar containers", which are basically init containers with restartPolicy: Always. The subsequent containers won't run until the startup probe for the init container has passed. Currently, Podman does not allow startup probes in init containers, giving the following message:

Error: playing YAML file: cannot create an init container that has either of lifecycle, livenessProbe, readinessProbe, or startupProbe set

Having this feature enables useful local orchestration, as you get better control over the order in which containers are run.

Suggest potential solution

It would be brilliant if Podman could remove the limitation described above, and allow ordering of init containers as sidecars.

Have you considered any alternatives?

No response

Additional context

No response