-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cron container now requires Redis parameters to function #1763
Comments
For what it's worth, I found it much cleaner/easier to build my own Docker image (following the examples included in this repo) and run cron in the main nextcloud container using supervisor/supervisord. Reasons here: #253 (comment) |
Hi @eric-pierce Thanks for your report. It would have been very interesting to see your /var/www/html/config.php when this happened (and possibly still today). Do you have a My best guess is that somehow your This would have "worked" but required REDIS_* variables to be passed to both your app and cron containers (rather than the cron container picking up the appropriate config from your shared volume's The main scenario I can think of this happening in is if you didn't originally install NC with REDIS_* variables, but later added them. |
Closing due to inability to replicate and insufficient info to proceed at the moment. Your To avoid this either:
I personally tend to stick with approach two, since things are often changed later and not all environment variables propagate the same way. This is also necessary for other runtime only variables like the |
I'm running two containers as part of my install, one for the main application and one for the cron job. With the latest update (either of Redis to 7.0 or of Nextcloud to 24.0.1, I'm not sure) the cron container crashes unless the two REDIS environment variables are passed into it or present in the env file, so no background jobs are run.
Without the environment variables I had the following output from my cron container:
By adding the Redis environment variables, the cron job runs as expected.
My docker compose is below - the last two lines were what I added to fix the issue.
The text was updated successfully, but these errors were encountered: