从源码构建Python和Pip后移动路径引发解释器错误的解决咨询

You're spot-on about the root cause: when you install pip via get-pip.py, it creates executable scripts (like pip, pip3, pip3.6) in the bin directory with a hardcoded shebang line pointing to the Python interpreter path that existed during installation. When you move the entire Python directory, that path becomes invalid, triggering the "bad interpreter" error.

Here are actionable solutions tailored to both fixing an existing moved installation and adjusting your Dockerfile to avoid the issue altogether:

1. Immediate Fix for an Already Moved Installation #

If you’ve already relocated the Python directory and need to repair pip right away, choose one of these quick options:

Option A: Manually Update Shebang Lines #

Head to the bin folder of your moved Python installation (/tmp/test/bin in your case) and edit each pip-related script. Change the first line from:

#!/opt/python/3.6.5/bin/python3.6

to:

#!/tmp/test/bin/python3.6

This works for one-off scenarios but gets tedious if you have multiple Python versions or scripts to update.

Option B: Reinstall Pip Using the Moved Python Interpreter #

Since the relocated Python is still functional, use it to rerun get-pip.py and target the new installation path. This will regenerate pip scripts with the correct shebang:

/tmp/test/bin/python3.6 /get-pip.py \
    --prefix /tmp/test \
    --disable-pip-version-check \
    --no-cache-dir \
    --no-warn-script-location \
    pip==20.2

If get-pip.py is still available in your container, this command will overwrite broken pip scripts with working ones.

2. Optimize Your Dockerfile to Prevent the Issue #

The cleanest approach is to adjust your Dockerfile so pip is installed after moving Python to its final location. This ensures pip’s shebang uses the correct path from the start.

Here’s the revised Dockerfile:

FROM buildpack-deps:stretch
ARG PYTHON_VERSION="3.6.5"
ARG PIP_VERSION="20.2"
ARG INSTALLATION_PREFIX="/opt/python/${PYTHON_VERSION}"
ARG FINAL_PREFIX="/tmp/test"

WORKDIR /usr/src/python

# Fetch Python source and install build dependencies
RUN wget -q https://www.python.org/ftp/python/$PYTHON_VERSION/Python-${PYTHON_VERSION}.tgz \
 && apt-get update \
 && apt-get install -y \
    make \
    build-essential \
    libssl-dev \
    zlib1g-dev \
    libbz2-dev \
    libreadline-dev \
    libsqlite3-dev \
    wget \
    curl \
    llvm \
    libncurses5-dev \
    libncursesw5-dev \
    xz-utils \
    tk-dev

# Extract source archive
RUN tar xvf Python-${PYTHON_VERSION}.tgz \
 && rm -f Python-${PYTHON_VERSION}.tgz

# Compile and install Python to temporary prefix
RUN cd Python-$PYTHON_VERSION \
 && ./configure \
    --prefix=${INSTALLATION_PREFIX} \
    --build=$(dpkg-architecture --query DEB_BUILD_GNU_TYPE) \
    --enable-loadable-sqlite-extensions \
    --enable-shared \
    --with-system-expat \
    --with-system-ffi \
    --without-ensurepip \
 && make -j $(nproc) \
 && make altinstall

# Move Python to final destination FIRST
RUN mv ${INSTALLATION_PREFIX} ${FINAL_PREFIX}

# Update environment variables to point to the final path
ENV LD_LIBRARY_PATH="${FINAL_PREFIX}/lib:$LD_LIBRARY_PATH"
ENV PATH="${FINAL_PREFIX}/bin:$PATH"

# Install pip using the relocated Python interpreter
RUN wget -q https://bootstrap.pypa.io/get-pip.py -O /get-pip.py \
 && ${FINAL_PREFIX}/bin/python3.6 /get-pip.py \
    --prefix ${FINAL_PREFIX} \
    --disable-pip-version-check \
    --no-cache-dir \
    --no-warn-script-location \
    pip==${PIP_VERSION}

WORKDIR /

By moving Python before installing pip, you ensure pip’s scripts are generated with the correct final path in their shebang lines, eliminating post-move fixes entirely.

3. Alternative: Force-Reinstall Pip via Python Module #

If you can run the relocated Python interpreter (even with a broken pip), use Python’s module system to invoke pip and force a reinstall. This will regenerate scripts with the correct path:

/tmp/test/bin/python3.6 -m pip install --upgrade --force-reinstall --prefix /tmp/test pip==20.2

This bypasses the broken pip script and uses the Python interpreter directly to run the pip module, ensuring fresh, correctly configured scripts.

内容的提问来源于stack exchange，提问作者Kiran