Hi Mohamed,
This was caused by a recent update in the python cryptography package. The easiest fix is to pin the package version by adding cryptography = "<3.4"
under the [packages]
section in Pipenv
. Make sure you run pipenv lock
and commit the updated of version of Pipenv.lock
as well.
Alternatively if you want to use the most recent version of cryptography you’d have to add Rust build dependencies in Dockerfile.
1 Like
Hi @Crowdbotics_Dan thank you so much for your support, our current version is actually cryptography==3.3.1
and we are using requirements.txt
is it might be another way? or should i go with Rust build thing?
@mohamed.youssef, the Dockerfile runs off Pipfile.lock
. Please make sure you add the necessary dependencies to Pipfile and then run pipenv lock
.
You can read more about Pipenv here - pipenv · PyPI
Hi @dmitrii.k @Crowdbotics_Dan , we are using requirements.txt
not pipenv, so it should install from there directly, right?
also the version of cryptography
we have is 3.3.1
shouldn’t that be good?
Hi @mohamed.youssef,
Your production uses Docker. Your repository contains a Dockerfile
that describes the docker image that runs in production. That docker image uses pipenv
in production. Please refer to your README for more information about that.
You’re free to modify the Dockerfile to make it suit your process. I encourage you to test locally using Docker Compose - this will ensure you build and run the same image that will build and run in production before deploying it.