(NekoSock) Miya Ironami :verified_trans: on Nostr: Okay to be fair to the Podman project, it's not an oversight on their end. The ...
Okay to be fair to the Podman project, it's not an oversight on their end.
The problem is that, on systemd, user services can't wait for network-active.target. So they have a user service that checks regularly if network-active has fired yet. The service ends when it does, and all the containers start.
However, systemd will not bother firing network-active.target if nothing depends on it, which is the case on a blank CoreOS install. The workaround is to create a dummy system service that depends on network-active.
https://github.com/containers/podman/issues/24796
It's fair to say there is not much Podman can do about that, and it's rather up to systemd to provide a solution for user services to wait for non-user targets.
The problem is that, on systemd, user services can't wait for network-active.target. So they have a user service that checks regularly if network-active has fired yet. The service ends when it does, and all the containers start.
However, systemd will not bother firing network-active.target if nothing depends on it, which is the case on a blank CoreOS install. The workaround is to create a dummy system service that depends on network-active.
https://github.com/containers/podman/issues/24796
It's fair to say there is not much Podman can do about that, and it's rather up to systemd to provide a solution for user services to wait for non-user targets.