CryptographyDeprecationWarning

ODM
#1

Hi everyone,

I’m running Docker Toolbox on w Windows 8 host, but I’m having a problem and I can’t find a solution anywhere.

After pulling the images, I got the error “CryptographyDeprecationWarning”, as seen in the attachment. I’ve used Docker Toolbox and Docker Desktop recently and other machines and have not come across with this problem, but they all have been Windows 10 host (Home and Pro respectively)

Hope anyone has any idea as to why this is happening, because I can’t find anything related to it.

Kind regards,

José

MicrosoftTeams-image
MicrosoftTeams-image1920×2559 648 KB

#2

It’s just a warning. It shouldn’t stop the program from working. Perhaps there’s some other issue?

#3

Thanks pierotofy, that was my first thought, but the problem is that the process stops at that point, and I can’t find any other flag that let me force the processing despite that warning. Is there something else I can put in my command to bypass that?

#4

I just ran this with the latest ODM:

D:\shared\datasets>docker run -ti --rm -v d:/shared/datasets/brighton/:/datasets/code opendronemap/odm --project-path /datasets
/usr/local/lib/python2.7/dist-packages/cryptography/__init__.py:39: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in a future release.
  CryptographyDeprecationWarning,
[INFO]    Initializing ODM - Fri Aug 21 16:01:46  2020
[INFO]    ==============
[INFO]    build_overviews: False
[INFO]    camera_lens: auto
[INFO]    cameras: {}
[INFO]    crop: 3
....

I would guess it’s some problem with the docker toolbox shell? Try to use powershell /command prompt.

1 Like
#5

Thank you very much, I will try that. Yes, I’ve run it on other machines, using both Docker Toolbox and Docker Desktop and haven’t had this trouble, is just with this specific PC. But I will try as you suggest, thank you very much!

1 Like
#6

I’m so sorry for wasting your time, the person I was trying to assist with this problem didn’t have the folder images inside the working directory. I feel dumb for not making sure of that in the first place.

Anyway, thanks again for your help @pierotofy.

Kind regards,

1 Like
#7

No worries! Glad you found out the cause. :+1:

1 Like