Add CKAN 2.11 images

[amercader]

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.

[amercader]

Images pushed to Docker Hub

[kowh-ai]

@amercader - both base and dev images build OK

[kowh-ai]

@amercader - images build fine however I get errors when using these 2 new images

1. Using the base image I get an error when adding a new resource to a dataset
   

2. Using the dev image I get a different error

I can work on this next week to see what config options may be missing here

[amercader]

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

[amercader]

Can you review and merge ckan/ckan#8310 @kowh-ai, that should take care of the first exception

[amercader]

Just tried issue 2 and worked for me. Make sure that CKAN__DATAPUSHER__CALLBACK_URL_BASE and DATAPUSHER_REWRITE_URL are correctly set using ckan-dev instead of ckan.
We probably need separate .env.example and .env.dev.example files because there's a few of these options that are different across environments.

[kowh-ai]

@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 CKAN__DATAPUSHER__CALLBACK_URL_BASE and DATAPUSHER_REWRITE_URL to use ckan-dev but they did "go away" and I couldn't recreate the same error. Anyway, I'll create a PR on the ckan-docker repo for a README change to detail what to change in the .env file when moving from base to dev mode

[amercader]

@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

[wardi]

needing to update the .env and using/not using -f docker-compose.dev.yml isn't ideal. Maybe we can use the same docker compose for both dev and prod and use a setting to switch instead?