Docker镜像生产环境构建失败(mysql-client无安装候选)，开发环境正常

First, let's address your confusion about Docker's consistency promise — you're right in theory, but there's a critical catch with tagged base images that aren't pinned to a specific immutable version. Here's what's going on:

Root Causes #

• The python:2.7 base image is a moving target: This tag points to a Debian-based image, but as Debian releases reach end-of-life (like Jessie, which Python 2.7 originally relied on), their official repositories get archived. The mysql-client package might no longer be available in the default repos for the updated base image your production server pulled, while your dev machine still has a cached older version of the base image where the package existed.
• Package name shifts or repo removal: In newer Debian versions (or archived repos), the mysql-client package may have been renamed (e.g., to default-mysql-client) or pulled entirely from the default sources list.

Fixes to Ensure Consistent Builds #

1. Pin your base image to a specific immutable version #

Instead of using python:2.7, use a precise tag that won't change, like python:2.7.18-jessie (the final Python 2.7 release paired with Debian Jessie). This locks in the exact base OS and Python version, so both dev and prod use identical environments:

FROM python:2.7.18-jessie

2. Update apt sources to use Debian's archive repos #

If you need to stick with python:2.7 (though pinning is far more reliable), replace the default apt sources with Debian's archive servers for the old release. Add this right before your apt-get update command:

RUN echo "deb http://archive.debian.org/debian jessie main" > /etc/apt/sources.list \
    && echo "deb http://archive.debian.org/debian jessie-updates main" >> /etc/apt/sources.list \
    && apt-get update && apt-get install -y \
    # ... your full list of packages here

This ensures you're pulling packages from the archived repos where mysql-client is still hosted.

3. Replace mysql-client with a compatible alternative #

If archive repos aren't working for you, try swapping mysql-client for default-mysql-client — this is a metapackage that points to the available MySQL client in the current OS release:

RUN apt-get update && apt-get install -y \
# ... all your other packages
default-mysql-client \
# ... remaining packages

4. Test fresh builds with --no-cache regularly #

On your dev machine, run docker build --no-cache . periodically to simulate a clean build (just like your production server does). This will reveal inconsistencies where cached layers were hiding repo changes.

Key Takeaway #

Docker's consistency depends on pinning images to specific, immutable tags — using floating tags like python:2.7 means your base image can shift over time, leading to unexpected build failures. By pinning your base image and adjusting your apt sources appropriately, you'll align dev and prod builds again.

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