There is a wrong run order with userborn, where agefs is started after userborn, so userborn isn't able to pick up a hashed password file in the secret mount:
AFAIK it's a problem with regular agenix as well.
But the other case, if userborn is started after agefs, will mean that agefs won't be able to read usernames/groupnames for users created by userborn. So perhaps userborn should run, then agefs runs, then userborn is restarted?
There is a wrong run order with userborn, where agefs is started after userborn, so userborn isn't able to pick up a hashed password file in the secret mount:
AFAIK it's a problem with regular agenix as well.
But the other case, if userborn is started after agefs, will mean that agefs won't be able to read usernames/groupnames for users created by userborn. So perhaps userborn should run, then agefs runs, then userborn is restarted?