checkinstall | fix checkinstall for RHEL x64 ... fork

In your example, you actually never reach the part of code that handles input. These inputs only occur for interactive sessions - which Jupyter is not. You can check with

The second example should be:

Firstly: your build of Python should allow you to use python3 -m pip as your pip command. The -m flag is good practice anyway as it will make sure that you're associating the pip you use with the correct Python interpreter. So, the python-pip python3-pip install should not be necessary.*

Secondly: with regards to the SSL option, it's possible you might need python-openssl. I am, ironically, getting a server-side error when I try to search for this on packages.ubuntu.com, but it's shown in this up to date example alongside libssl-dev.

Here is a Dockerfile demonstrating both of the above points:

The newline convention is \r\n on windows. Bash interprets newline character as... newline character, and the \r is a normal character for bash.

Fix:

This appears to be a documented issue, that you'll find with a search of the error:

You installed the shared library addme.so in the wrong place.

It should be installed in the PostgreSQL library directory, not in /usr/lib/x86_64-linux-gnu. The PostgreSQL library directory can be found with

I tackled the problem by merging all the RUN command into one with a lot of '&& \'. This helped me get the image size down to 5.2 GB.

As another user has commented, wget does not write the data to stdout by default. There are two ways to fix your script:

This is a python compilation issue that has been fixed as of Python 3.4.5. Best practice would be to upgrade to 3.4.5 and follow the compilation steps again.

For those coming here for Python <3.5.3 with the same issue, this same issue has been fixed as of 3.5.3 (see here).

I am not sure if other Python versions are affected, but have seen in the Patch notes that in later versions also a fix was made for Windows and MacOSX. Please check the change log for the Python major version you are using to see which fix applies to you. the change logs can be found here: (Python 3.4, Python 3.5)