Upgrade to docker image 5.14.3 fails

[rac-HH]

In my docker stack I changed the image version from 5.12.2.3 to 5.13.3.5 in docker-compose.override.yml.
Taking the stack up was successfull.
Then I changed the image version from 5.13.3.5 to 5.14.3.2.
Taking the stack up results in endless restarts, logging:

weblate-1  | Starting Weblate 5.14.3...
weblate-1  | /app/bin/start: 125: /app/venv/bin/weblate: not found
weblate-1  | Failed to load configuration, please see errors above.

When starting the image seperately (without correct environment) it runs more steps:

$ docker run -it --rm --entrypoint /bin/bash weblate/weblate:5.14.3.2
weblate@8f3cf9459e0b:/$ /app/bin/start
Starting Weblate 5.14.3...
Generating Django secret...
Missing WEBLATE_SITE_DOMAIN, please configure it

The git checkout is up to date.
Any ideas how to fix it?

[nijel]

What happens when you start /app/venv/bin/weblate manually?

Anything special in the docker componse configuration? Like volumes besides documented ones or changes to PATH?

[rac-HH]

Thank you for your fast reply.

While answering your questions I found the problem. Some image versions ago, entering the container via "docker compose exec weblate bash" complainted that the home directory is not writeable. So I added a volume for it overlooking the hidden .local directory.

Often the right question helps - thank you again.

[nijel]

But still, this placement of Python is unfortunate, WeblateOrg/docker-base#323 should fix that.

[rac-HH]

I found a more urgend reason for my additional volume: borg needs some writable directories in weblate home. Now I use this volumes:

      - ./weblate_home_config:/home/weblate/.config
      - ./weblate_home_cache:/home/weblate/.cache

[nijel]

Weblate executes borg internally with a different HOME. If you use the container manually, disabling read only might be the best appraoch.