[5.7.2.2 -> 5.8.3.1] Fontconfig errors during upgrade

[gourvy]

Describe the issue

I use an instance of Weblate in kubernetes, with kustomize instead of helm. I tried to upgrade from 5.7.2.2 to 5.8.4.1 but got a problem (I'll create a different issue), so I I upgraded to 5.8.3.1 instead. It works fine but I have the following error messages at start:

celery-notify stderr | Fontconfig error: "/app/data/fonts/fonts.conf", line 1: no element found
celery-notify stderr | Fontconfig error: Cannot load config file from /app/data/fonts/fonts.conf
celery-notify stderr | Fontconfig error: No writable cache directories
celery-notify stderr | Fontconfig error: No writable cache directories
celery-notify stderr | Fontconfig error: No writable cache directories
celery-notify stderr | Fontconfig error: No writable cache directories

I use a read-only filesystem with /app/data being a read/write volume.

After weblate started, I checked and the file /app/data/fonts/fonts.conf exists.

After restarting the container (pod/deployment) the problem doesn't seems to appear, so I guess it's only during migration.

I already tried

• I've read and searched the documentation.
• I've searched for similar filed issues in this repository.

Steps to reproduce the behavior

Start a weblate container 5.7.2.2 (with db, redis, data volume, etc.), then migrate to 5.8.3.1

Expected behavior

No response

Screenshots

No response

Exception traceback

No response

Additional context

No response

[nijel]

Most likely, this is an outcome of #2923

[gourvy]

After modifying my deployment to upgrade an other instance of weblate from 5.7.2.2 to 5.8.4.1 (with no error than the fontconfig errors), I encountered the same error messages. So, I don't think this minor problem is linked to #2923

[nijel]

Can you please share content of /app/data/fonts/fonts.conf?