Closed rfdrake closed 2 years ago
It looks like a package installed by https://github.com/peering-manager/docker/blob/9ae083caed413607164529ceb3d6df845bd70299/Dockerfile#L25 is causing the issue and overrides the pinned Django version found in requirements.txt
.
Can you test the latest image (pushed a few seconds ago) to see if it fixes this issue?
That fixed it. Thanks very much!
For some reason the docker images are being built with Django 4.0 instead of 3.x. I tried both the "latest" image and the "snapshot" image and got the same problem:
Running "pip list" inside the container shows it's using Django 4.0 despite the requirements file saying >=3.2,<3.3.