-
Notifications
You must be signed in to change notification settings - Fork 4
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
fix crontab in ckan_run_harvester #229
Conversation
…loading in ckan_run_harvester
Image has been pushed to cioos/ckan Testing Quick StartPull image
Remove Home Volume and Restart
for full documentation see TBD |
For reasons unknown, this is what's happening now. My guess is that we may need to downgrade the cryptography library to 38.0.4 - from looking around and testing that's that latest version that can support that import call. Similar error to this one: apache/superset#22613
|
hmmm I thought we fixed this one. I will check my package versions |
…ne and cause conflicts if they are not disabled) Updated Dockerfile to lock pyopenssl and cryptography to the highest versions that still support x509 in the manner that the ckan harvester expects
it seems like the command line tools need the .plugins list in the ckan.ini however. perhaps we need to write to the ckan.ini on container start or something |
…ith other containers
I beleave with the addition of the ckan_home volume to the ckan_run_harvester this issue is now fixed. please confirm and merge if it is working. |
The harvester now runs well without any external intervention but the entrypoint file still doesn't seem to be able to setup the cronjobs on its own. However, I have found that if I manually execute command to setup the crontab from within the container via an interactive shell then, the cron jobs will populate and then execute properly. The container loses the cronjobs if they are rebuilt though... A thought occurs - could we just mount the crontabs file as a volume like what we're doing with the entrypoint files? I'll test that out on my local to see how it performs. |
- commented out crontab setup line in entrypoint - crontab file in contrib/docker needs to be owned by root:root in order to execute
Mounting the |
… in /docker-entrypoint.d/ckan-run-harvester-entrypoint.sh is only run once on the first container start and never again until attached volumes are cleared
I pushed a fix for the crontab that does not require mounting. the entrypoint file was not being run as it is only run on the first container start if located under docker-entrypoint.d and not run again until attached volumes are cleared. this is great for the other containers but not this one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been working well on my end and we have clear feedback in the log that the cron jobs are being added.
fix #227
update config so command line tools can load extensions. fix crontab loading in ckan_run_harvester