Hi everybody,
I am trying to set up Nupic in Docker. I followed the instructions at the beginning this thread and things seem to work. I can run all the commands, check out the tutorials etc.
More specifically, on running:
sudo docker run -i -t numenta/nupic /bin/bash
it pulls the image from Dockerhub, starts it up, and drops me into the shell. From there, I can open up python interpreter, or create a script or whatever in the container and start playing with Nupic libraries - all good so far.
However I wanted to change some things in the Dockerfile to customise it a little, mostly just to add some applications and libraries I like having in my dev environment - I also wanted to have the container be able to see my local machine files, so set up a bind mount kind of thing, which usually seems really easy with Docker.
But the problem is that if try and build this image directly from the Dockerfile (at: https://hub.docker.com/r/numenta/nupic/dockerfile) rather than pulling it, it doesn’t seem work - when I downloaded the Dockerfile and ran docker image build -t mycustomnupicimage I get the following error:
Collecting setuptools
/tmp/tmpze03H0/pip.zip/pip/vendor/requests/packages/urllib3/util/ssl.py:122: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
Downloading https://files.pythonhosted.org/packages/42/3e/2464120172859e5d103e5500315fb5555b1e908c0dacc73d80d35a9480ca/setuptools-45.1.0.zip (859kB)
Could not import setuptools which is required to install from a source distribution.
Please install setuptools.
Investigating this leads to lots of issues that mostly come python from 2.7 deprecation issues:
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip...
I am trying to get around it by just stating with a python:2.7 image but running into lots of issues.
Just wondering if anyone has some ideas around this - what I really want is to set things up more along the lines of the solution being explored at: Docker, jupyter and HTM , though I can’t make that work either.
Does anyone have any suggestions? - Apologies if I am missing some kind of Docker issue here, its usually pretty plug and play, so I haven’t had to troubleshoot things like this too much.