-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add CKAN 2.11 images #69
Conversation
These are the same py3.10 based ones as the master ones
Images pushed to Docker Hub |
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.
@amercader - both base and dev images build OK
@amercader - images build fine however I get errors when using these 2 new images
I can work on this next week to see what config options may be missing here |
Thanks @kowh-ai 1 is probably a problem with my fix in ckan/ckan#8284 and 2 looks like a networking problem with the datapusher container. I'll investigate as well |
Can you review and merge ckan/ckan#8310 @kowh-ai, that should take care of the first exception |
Just tried issue 2 and worked for me. Make sure that |
@amercader - Yes all of the images work for me now (after a day of testing). I did have the same networking (cannot connect to datapusher) issues in 2.10 and 2.11 and I had updated |
@kowh-ai yes I had different issues when recreating environments, specially when switching between the prod/dev ones. Basically you need to remove everything including volumes to avoid issues. I suspect the site_packages one is to blame in many cases , eg packages from project images not being installed |
needing to update the .env and using/not using |
These are the same py3.10 based ones as the master ones.
There's lots of duplicated files, we should aim to have a common directory for these unless a specific version needs to override a particular file for some reason.