如何创建已完成初始化的MySQL Docker镜像？

Hey there! Let's figure out how to build a pre-initialized MySQL 5.7.21 image for your staging environment—solving both the "run-on-first-start" initialization and bloated image size problems you mentioned.

The core issue with your original approach is that the init scripts only run when the container starts for the first time, and those scripts (plus any temporary setup files) stick around in the image, adding unnecessary bulk. Instead, we can use multi-stage Docker builds to pre-run the initialization in a temporary "builder" stage, then copy only the finalized database data into a clean base image.

Here's a complete, commented Dockerfile that does exactly this:

# Stage 1: Builder - Run initialization and capture the prepared database data
FROM mysql:5.7.21 as builder

# Set environment variables required for initialization
ENV MYSQL_ROOT_PASSWORD=your-root-password
ENV MYSQL_DATABASE=your-target-db
ENV MYSQL_USER=your-db-user
ENV MYSQL_PASSWORD=your-user-password

# Copy your initialization scripts (SQL, tar, etc.) into the init directory
COPY ./init /docker-entrypoint-initdb.d

# Initialize MySQL, run all init scripts, then cleanly shut down the service
RUN \
  # Initialize MySQL with insecure mode (no root password yet)
  mysqld --initialize-insecure --user=mysql \
  # Start the MySQL server in the background
  && mysqld --user=mysql & \
  # Wait until MySQL is fully ready (more reliable than fixed sleep)
  && until mysqladmin ping -h localhost --silent; do sleep 1; done \
  # Set the root password
  && mysql -u root -e "ALTER USER 'root'@'localhost' IDENTIFIED BY '${MYSQL_ROOT_PASSWORD}';" \
  # Execute all SQL scripts in the init directory
  && for f in /docker-entrypoint-initdb.d/*.sql; do \
       mysql -u root -p${MYSQL_ROOT_PASSWORD} ${MYSQL_DATABASE} < "$f"; \
     done \
  # If you have compressed backups (e.g., .sql.gz), uncompress and run them first:
  # && for f in /docker-entrypoint-initdb.d/*.sql.gz; do \
  #      gunzip "$f" && mysql -u root -p${MYSQL_ROOT_PASSWORD} ${MYSQL_DATABASE} < "${f%.gz}"; \
  #    done \
  # Cleanly shut down MySQL to ensure data is written to disk
  && mysqladmin -u root -p${MYSQL_ROOT_PASSWORD} shutdown

# Stage 2: Final Image - Clean base image with pre-initialized data
FROM mysql:5.7.21

# Copy the pre-initialized database data from the builder stage
COPY --from=builder /var/lib/mysql /var/lib/mysql

# Set the same environment variables as the builder stage (required for startup)
ENV MYSQL_ROOT_PASSWORD=your-root-password
ENV MYSQL_DATABASE=your-target-db
ENV MYSQL_USER=your-db-user
ENV MYSQL_PASSWORD=your-user-password

# Ensure correct permissions on the data directory
RUN chown -R mysql:mysql /var/lib/mysql

• Instantly Ready for Staging: When you start a container from this image, MySQL will boot up with your pre-initialized database—no waiting for scripts to run on first start.
• Smaller Image Size: The final image doesn't include your init scripts, temporary setup files, or builder-stage artifacts. We only copy the essential /var/lib/mysql directory with the ready-to-use database.
• Consistent State: Every container started from this image will have the exact same database state, which is critical for reliable staging environments.

1. Keep Environment Variables Consistent: Make sure the MYSQL_* variables match exactly between the builder and final stages. Mismatched passwords or database names will cause startup failures.
2. Handle Compressed Files: If your init directory has .tar or .sql.gz files, adjust the builder stage to decompress them before running (see the commented example in the Dockerfile).
3. Wait for MySQL Properly: Using until mysqladmin ping ... is more reliable than a fixed sleep command—it ensures MySQL is fully ready before running your scripts, avoiding connection errors.
4. Test the Image: After building, run a container and verify your database schema/data exists:

   docker build -t preinitialized-mysql:5.7.21 .
   docker run -d --name test-db preinitialized-mysql:5.7.21
   docker exec -it test-db mysql -u root -pyour-root-password your-target-db -e "SELECT * FROM your-table;"
   

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