Closed ianathompson closed 3 years ago
I could not reproduce this, but it might be some issue in the version you were running before and got exhibited during the upgrade. The CI tests pass with current version as well, so it's most likely some upgrading issue of the redis container...
This issue has been automatically marked as stale because there wasn’t any recent activity.
It will be closed soon if no further action occurs.
Thank you for your contributions!
Describe the issue After doing the latest docker-compose pull for weblate, database and cache, the cache would not start. When reviewing the stderr output in Docker the system complains:
I already tried
Describe the steps you tried to solve the problem yourself.
command: redis-server --appendonly yes
as some other docker compose files do for redis. This still had the same error message.command: ["redis-server", "--appendonly", "yes"]
code and then randocker compose up cache --force-recreate
and the cache image loaded.command: ["redis-server", "--appendonly", "yes"]
code in the docker-compose.override.yml filedocker compose up --force-recreate
command on all of the images.Not sure if I missed a step or if something changed with 6.2.4.
To Reproduce the issue
docker compose pull Pulling weblate Pulling database Pulling cache
Expected behavior I expected the system to pull all the latest versions of the software, reload the configuration files and start up without issue. It did not.