LLDAP

Usually you would solve that by introducing a startup dependency on the DB, with a health check on the DB that tells you once it's up

another way to solve it (though it's a bit ugly) would be to have the equivalent of docker-compose's `restart: unless-stopped`

thanks for telling me the proper solution, I will look into it later

I forgot that this setting existed for a hot minute. it was set to OnFailure, which should mean that it will automatically restart the container if the container exits with an error, however, podman did not restart it

when I set it to Always, it restarted until lldap was finally able to connect to the database

so now I'm just wondering if this is podman's fault, or LLDAP returns a non-error exit code when in fact, it exited with an error

Hmm, yeah, there's a point at which I'm just logging an error instead of returning it

anyways, thank you so much for the help and making LLDAP, have a nice day! 🙂

Fixing it in there: https://github.com/lldap/lldap/pull/785 They don't actually make it easy