Replace Alpine with a Python (3.10) base image for CKAN 2.10 and master branches

[kowh-ai]

Fixes: #54

The objective is to upgrade from the alpine 2.17 base image to an official DockerHub Python 3.10 base image. We opted for a Debian 12 (bookworm slim) base image.

No alterations have been made to the current CKAN 2.9 builds.

Efforts were made to streamline the system libraries to only include essential components.

Upon successful testing and integration of this PR, several improvements will be realized:

• Implementation of Multi-Stage Builds, assuming it reduces image size and increases image security
• Optimization of Docker Layers and subsequent caching mechanisms
• Enhancements to render the base image more suitable for production environments
• Assess the feasibility of substituting Supervisor with a native Docker Compose (or Docker) approach for managing CKAN process restarts.
• Fix: Running "ckan -c ckan.ini db upgrade" on master fails #60

I'm happy to take suggestions for better naming of files and images

[kowh-ai]

@EricSoroos - if you get a chance would you please be able to take a look at this?

[amercader]

Does this file have any difference with the current start_ckan.sh? If not I think it would be great to avoid duplication, we have a lot of it already in this repo!

[kowh-ai]

Yes a couple of changes, probably the most significant one is that the python.3.10 one sets up a virtual environment

There's a change to the USWGI options too

Also, the start_ckan.python.3.10.sh file is copied as start_ckan.sh (ie: renamed)

[kowh-ai]

@amercader - Iv'e updated filenames, image names...got consistent with using ..-py3.. rather than python

[amercader]

@wardi can you share the approach you mentioned to autoactivate the venv when running a command in the container? cheers

[wardi]

@wardi can you share the approach you mentioned to autoactivate the venv when running a command in the container? cheers

Yes we can use https://docs.docker.com/reference/dockerfile/#entrypoint to run commands before other run commands etc. I used this in an old docker config to reset the UID of the ckan user to match the one from the mounted directory, become the ckan user and activate the virtualenv

[kowh-ai]

@amercader - I have committed your suggested change to rename the Dockerfile (for python) to remove the "dash" - Just confirming that this is what you want as I will need to update a few more things - thanks

[amercader]

@kowh-ai yes, this way is consistent with the tag ending in py3.10

[kowh-ai]

Linking the pip issue with alpine 3.19: "Python’s package directory is now marked as “externally managed” which means that pip can no longer install to system directory which is managed by apk. Users may use pipx instead"

[amercader]

@kowh-ai can you bring the new Dockerfile based on python:3.10-slim-bookworm to a stage where this issue occurs? It will be easier to decide what to do this way

I can't imagine that this issue hasn't been solved somehow on the official Python images

[kowh-ai]

@amercader - I was unsuccessful is recreating the pip issue using the python/bookworm base image. I'm really not sure why...anyway Iv'e made changes (commented out any venv lines) built all the images (locally) and tested. Maybe you could confirm they work and then we take it from there...