flask-bootstrap | Flask app template with integrated SQLAlchemy | Authentication library

Searching for the exception, leads to the corresponding eventlet issue: https://github.com/eventlet/eventlet/issues/687

The summary is that eventlet (0.32.0) is currently not compatible with Python 3.10 because it tries to patch types that have become immutable in Python 3.10.

Like with your requirements, it is good practice to be more specific with your Docker dependencies too. Today using the tag 3 for the Python Docker image will give you 3.10.0, unless it is using a cache. In the future it could be a different version. Since there is a compatibility issue with Python 3.10, use Python 3.9 - the currently latest Python 3.9 Docker tag is 3.9.7.

i.e. it should work once you change your first line of the Dockerfile to:

If you have a look for the base image, you could see it just be updated 27hours ago.

You're using old mysqlclient 1.3.12 with new MySQL 8. Either you need to downgrade MySQL to version 5.6. Or you need to use later mysqlclient.

The incompatibility was fixed in commit a2ebbd2 on Dec 21, 2017 so you need a later version of mysqlclient.

mysqlclient 1.3.13 was released on Jun 27, 2018. Try it or any later version.

The instructions Pip helpfully links you to explain what's going on, and it is indeed a bit of a hairy situation.

There is already an Beanstalk application that's running EC2s with docker containers that work just fine with these requirements so I'm not sure why this is happening now.

As to "why this is happening now" – two things I can think of:

• The Pip version in your base image has been updated; newer versions are smarter about conflicting dependencies (in that they refuse to install package constellations that might/should not work).
• Because your requirements.txt isn't necessarily fully locked down; there are transitive dependencies that get installed that aren't listed in the file that have become incompatible with one another.

However, since you already do have working container images, that's great! You could simply do

Check if your web app on PythonAnywhere is set up to be run by Python 2.7 -- I see you're using pip install outside of a virtual environment which by default will use pip for Python 2.7 as you can see in the output (btw. it won't work on PythonAnywhere, you need to provide --user option). If you want to install packages outside of virtual environment for different version of Python, use pipX.X install --user ... (where X.X should be replaced by required Python version). Also, remember to reload the web app every time the setup is changed. And if you're really stuck, maybe try contacting PythonAnywhere support (support@pythonanywhere.com) or use their forums?

There is an issue with the way you are initializing flask-bootstrap. This how you should go about it:

I'm looking for a solution for this exact question too, but all use flask-bootstrap and that is exactly what I don't want to use.

I've tried the following:

Your environment does not have access to an installation of wheel. You should be able to resolve this by adding the line:

RUN pip install wheel

to your dockerfile before you attempt to install your requirements file.

Edit: I missed that virtual environments were being utilized here. I would argue that using a virtual environment is unnecessary in this case unless the OP is using their docker instance to run multiple python applications in parallel. There are cases to be made for using this pattern, though that does not appear to be the case here. As such, my suggestion would be to do away with venv altogether and simply install all dependencies inside the docker instance python installation, which would convert every venv/bin/pip call to a simple pip call.

Try upgrading MarkupSafe to the latest release: