Docker镜像如何避免/usr/local/bin被覆盖，同时共存Python与Docker

Great questions—these are common pitfalls when combining multiple tools in Docker images, so let's break each down with clear explanations and actionable solutions:

1. How to prevent multiple Docker images from overwriting the /usr/local/bin directory? #

The main issue here is accidental file overwrites when copying content from different images (like in multi-stage builds) or installing tools that target the same directory. Here's how to avoid it:

• Copy individual files instead of entire directories: Instead of doing COPY --from=another-image /usr/local/bin /usr/local/bin (which replaces any existing files in /usr/local/bin that share names with those in the source), copy only the specific executables you need. For example:

  COPY --from=docker-image /usr/local/bin/docker /usr/local/bin/docker
  COPY --from=python-image /usr/local/bin/python /usr/local/bin/python
  

  This way, you add only the files you want without risking overwrites.

• Use separate directories for different tools: Store executables from different sources in unique subdirectories, then add those paths to your PATH environment variable so the system can find them. For example:

  # Copy Docker binaries to a dedicated directory
  COPY --from=docker-image /usr/local/bin /usr/local/docker-bin
  # Add the new directory to PATH
  ENV PATH="/usr/local/docker-bin:$PATH"
  

  Now both your original /usr/local/bin (with Python tools) and /usr/local/docker-bin (with Docker tools) are accessible via command line, no overwrites needed.

• Check for file conflicts upfront: In multi-stage builds, add a quick check to list files in the target directory before copying, so you can spot potential name collisions early:

  RUN ls -la /usr/local/bin  # Verify existing files before adding new ones
  

2. Where do Docker binaries go when building a second test image based on a Python image? How to install both Python and Docker so their executables live in /usr/local/bin? #

First, let's clarify: A standard Python Docker image doesn't include Docker binaries by default. If you're trying to add Docker to a Python image, the mistake many people make is either overwriting /usr/local/bin entirely or using multiple FROM commands (which resets the image to the last base image, losing previous content).

Here's how to properly combine both tools: #

Option 1: Multi-stage build (cleanest approach)

Use multi-stage builds to pull Python and Docker binaries from their official images, then combine them in a single final image:

# Stage 1: Grab Python runtime
FROM python:3.11-slim AS python-source

# Stage 2: Grab Docker binaries
FROM docker:24.0.6 AS docker-source

# Stage 3: Final image with both tools
FROM debian:bookworm-slim

# Copy Python's core files (executables + libraries)
COPY --from=python-source /usr/local/bin /usr/local/bin
COPY --from=python-source /usr/local/lib /usr/local/lib

# Copy only the Docker binaries we need (avoids overwriting Python files)
COPY --from=docker-source /usr/local/bin/docker /usr/local/bin/docker
COPY --from=docker-source /usr/local/bin/dockerd /usr/local/bin/dockerd

# Install system dependencies for both tools
RUN apt-get update && apt-get install -y --no-install-recommends \
    ca-certificates \
    libssl-dev \
    && rm -rf /var/lib/apt/lists/*

# Verify both tools work
RUN python --version && docker --version

Option 2: Install Docker directly in the Python image

If you prefer a single-stage build, download Docker's static binaries directly into the Python image:

FROM python:3.11-slim

# Install dependencies to download Docker
RUN apt-get update && apt-get install -y --no-install-recommends \
    curl \
    ca-certificates \
    && rm -rf /var/lib/apt/lists/*

# Download and extract Docker binaries, then copy to /usr/local/bin
RUN curl -fsSL https://download.docker.com/linux/static/stable/x86_64/docker-24.0.6.tgz | tar xz -C /tmp \
    && cp /tmp/docker/docker /usr/local/bin/ \
    && cp /tmp/docker/dockerd /usr/local/bin/ \
    && rm -rf /tmp/docker

# Verify installation
RUN python --version && docker --version

Why your Docker binaries might have "disappeared" #

If you used multiple FROM commands without COPY --from, the final FROM (e.g., FROM python:3.11) replaces the entire image filesystem, wiping out any Docker binaries from earlier stages. Always use COPY --from in multi-stage builds to carry over files from previous stages.

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