It seems a problem with the docker python client. After running docker-compose for the first time. You get the error ImportError: No module named ssl_match_hostname on init
The fix is cp -r /usr/local/lib/python2.7/dist-packages/backports/ssl_match_hostname/ /usr/lib/python2.7/dist-packages/backports
Hi! I'm Rohan, a Full Stack Software Engineer, with a background of working with Deep Learning and AI, who loves to use his skills to create products that are at the intersection of all of these!
Hi! I'm Rohan, a Full Stack Software Engineer, with a background of working with Deep Learning and AI, who loves to use his skills to create products that are at the intersection of all of these!
After removing configparser docker-compose starts as expected.
I removed after installing compose via pip but noted an error related to configparser at end of install so this might be better run after dependencies but before compose. This part I haven't tried
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It seems a problem with the docker python client. After running docker-compose for the first time. You get the error
ImportError: No module named ssl_match_hostname on initThe fix is
cp -r /usr/local/lib/python2.7/dist-packages/backports/ssl_match_hostname/ /usr/lib/python2.7/dist-packages/backportsHmm, this is weird did you try to install it with Python 3?
Python 2 support ends next year.
Update, in the next few weeks, I'll rewrite this and try again on a fresh installation that should help me find the errors.
I was just using the standard installers as listed in your instructions (which are great BTW). Everything from first glance still uses Python2.
Yeah, you are correct, I just re-read my own post and yep everything seems to be using Python 3 😅
Please disregard my last comment.
I'll update the post and fix the remaining issues soon, that should help with my confusion.
Just out of curiosity how did you manage to fix the problem? By copying the dependency? I haven't seen this solution ever before.
This is specific to ARM Docker deployments. The Ubuntu deployments in the Cloud don't seem to have this issue.
I found people having the similar issue after installing docker-compose - github.com/docker/docker-py/issues...
this might be a better option.
After removing configparser docker-compose starts as expected.
I removed after installing compose via pip but noted an error related to configparser at end of install so this might be better run after dependencies but before compose. This part I haven't tried