thielj

Probably related, as the pool currently defaults to a minimum of zero connections. https://github.com/lldap/lldap/discussions/910 https://github.com/lldap/lldap/pull/1248#issuecomment-3250818457

@nitnelave happy to include this with the recent PR as I have a similar scenario. @peter- would you have some info about how you've setup litefs?

There isn't - except for writing a test value and catching the error. The suggestion here is simply to treat the database as if it was read-only. Not run the...

Thanks @peter- I'll need to look deeper into this setup. A version of LLDAP that can be configured as read-only (and with the UI disabled except for the health check)...

I suggested to WSL that they check cloud-init status before shutting down, as documented here: https://cloudinit.readthedocs.io/en/latest/howto/status.html @blackboxsw Not sure what your definition of complex user data is. Mine surely doesn't...

@CarlosNihelton I've described a workaround over on the WSL issue, which showed an additional problem with /etc/resolv.conf disappearing and package upgrades failing. I've added a workaround for that, too. https://github.com/microsoft/WSL/issues/11602#issuecomment-2140755462...

@CarlosNihelton Damn, I should have seen this document before - it looks almost identical to the workarounds I came up with. I'll need to try if the `--no-launch` and `--root`...

It might help to (a) emphasize that running `ubuntu2404.exe run cloud-init status --wait` _immediately_ after installation has completed is not just about watching cloud-init do its job - it's rather...

I'm not asking to provide any details of these tests as a response, a simple single 200 or 404/500 status code for the whole set is sufficient. `/api/health` is liveliness...

"Would Authelia still pass its own start checks" ? 200 : 404;