kowh-ai
commented
4 months ago Yes this issue affects an upgrade to 3.19 (3.18 builds fine)
Will investigate further...
UPDATE 1:
pip / pip3 are no longer able to be used to install CKAN in 3.19. It seems pipx is now the way to install applications and libraries. pipx by default will install into a virtual (isolated) environment.
The default location path pipx will use for the virtual environment is ~/.local/share/pipx however this can be overridden using PIPX_HOME which will place the virtual environment in the $PIPX_HOME/venvs/ directory. I’m not sure how easy it will be to make the necessary changes to be able to upgrade to Alpine 3.19 yet.
If it's too much effort given we are potentially moving to Ubuntu or Debian-slim as a base image this may have to be abandoned
UPDATE 2
Not mandatory to use pipx. We can create a Python virtual environment, run pip3 from there and update the uwsgi options to use --virtualenv /srv/app
| image | builds ok? | tested? |
|---|---|---|
| 2.10.4 base | yes | yes |
| 2.10.4 dev | not yet | not yet |
| 2.9.11 base | error | not yet |
| 2.9.11 dev | not yet | not yet |
| master base | yes | yes |
| master dev | not yet | not yet |
As the version of python that comes with alpine 3.19 is 3.11 I'm inclined to think we should abandon upgrading the CKAN 2.9 images
UPDATE 3
The Python 3.10 (bookworm slim) base image has this pip issue too
3.19 seems to be the latest one available:
https://alpinelinux.org/releases/
From the upgrade notes, it's worth checking if this would affect us: