SSSD database version errors on startup

[mikkonie]

We noticed that there are some SSSD errors on startup when running the SSSD build of the server in staging:

irods-1  | (Tue Feb 11 16:07:27:723087 2025) [sss_cache] [sysdb_domain_cache_connect] (0x0010): DB version too new [0.22], expected [0.21] for domain XXXXXXXX!
irods-1  | Lower version of database is expected!
irods-1  | Removing cache files in /var/lib/sss/db should fix the issue, but note that removing cache files will also remove all of your cached credentials.
irods-1  | Could not open available domains
irods-1  | groupadd: sss_cache exited with status 71
irods-1  | groupadd: Failed to flush the sssd cache.

PAM logins via SSSD still work without problems, so this doesn't seem to be a critical issue. Alas, I'd still prefer not seeing error messages on startup..

[mikkonie]

I suspect this may be simply caused by the ancient version of our SSSD image. See bihealth/sssd-docker#1.

Also, clearing the cache does not work.

[mikkonie]

See also bihealth/sodar-docker-compose#83.