Image not buildable due to default Python image now referring to `bullseye`

[awtimmering]

The Dockerfile in django-docker-box is not buildable in the current state, because:

• It uses python:${PYTHON_VERSION}-slim which implies latest
• latest has been updated from buster to bullseye as of August this year (discussion)
• some of the dependencies that are apt-get installed no longer exist with the same name, causing the build to fail (libgdal, libenchant)

So we should either pin the python image to the now older buster, or pin it to bullseye and update the packages. I will submit & propose a PR to do the latter.

[awtimmering]

Have added a PR.

NOTE: For anyone reviewing & trying this, please note that recent releases of docker-compose (2.10.9 - 2.10.10) have a bug that causes an error when you try to run the tests. This is related to the fact that our docker-compose.yml has refers to different absolute paths with context and Dockerfile , see https://github.com/docker/compose/issues/8971 for details. Bug is fixed in (pre-release) v2.2.0, which you can download.

awtimmering @ ~/django-docker-box - [main] $ docker-compose run --rm sqlite
[+] Running 2/0
 ⠿ Container django-docker-box-memcached-1   Created                                                                                         0.0s
 ⠿ Container django-docker-box-memcached2-1  Created                                                                                         0.0s
[+] Running 2/2
 ⠿ Container django-docker-box-memcached-1   Started                                                                                         0.5s
 ⠿ Container django-docker-box-memcached2-1  Started                                                                                         0.4s
Error response from daemon: path /home/awtimmering/django is mounted on / but it is not a shared mount.