[SOLVED] Why does my python project in the docker not start after a year after the last successful launch, despite the dependencies fixed with pipenv?

Why does my python project in the docker not start after a year after the last successful launch, despite the dependencies fixed with pipenv?

I have a python project that I previously ran successfully in docker containers, with all dependencies and package versions fixed using pipenv. However, when I tried to launch the project again in Docker after a one year, I encountered several errors.

I'm trying to understand why it worked before but now fails.

Here are some points to consider:

Fixed Dependencies: I ensured that all dependencies were pinned in the Pipfile.lock.
Docker Setup: My dockerfile and docker-compose.yml have not changed since the last successful run.
Error Messages: I am seeing various errors due to packages incompatibility.

I thought about updating the versions of all my packages and libraries, but it's a bad idea, because after that the project code may partially or completely stop working.

Please don't judge the question harshly, because I really don't know what to do with all this.

Solution

So I come up with this: I couldn't update dependencies due to that newer versions of pipenv don`t support python 3.7, so I installed older version of pipenv, succefully updated some packages and launched the project.