具备基础Docker知识，如何演示其能力以说服他人认可其价值？

Great question—let’s skip the dry textbook explanations and jump straight to hands-on, show-don’t-tell demos that’ll make anyone see how Docker streamlines real-world workflows. These are all quick, actionable examples you can run in 5-10 minutes:

1. Kill the "It Works on My Machine" Nightmare #

This is the most relatable pain point for any team. Show how Docker eliminates environment conflicts entirely:

• First, create a simple Python script app.py that relies on a specific dependency version:

  import pandas as pd
  df = pd.DataFrame({"Name": ["Alice", "Bob"], "Age": [30, 25]})
  print("Sample DataFrame:")
  print(df)
  

• Write a Dockerfile to package the app with its exact environment:

  FROM python:3.9-slim
  WORKDIR /app
  COPY app.py .
  RUN pip install pandas==1.3.5  # Pin a specific version to avoid surprises
  CMD ["python", "app.py"]
  

• Build the image:

  docker build -t demo-data-app .
  

• Now, run it on any machine with Docker installed—even one that has no Python or pandas at all:

  docker run --rm demo-data-app
  

  The output will be identical every time, no matter the host environment. Highlight how this eliminates hours of debugging dependency conflicts between team members or staging/production.

2. Spin Up a Complex Service Stack in 2 Minutes #

Show how Docker Compose turns tedious setup into a single command. Let’s use a WordPress + MySQL stack (but you can swap this for any service combo your audience cares about):

• Create a docker-compose.yml file:

  version: '3.8'
  services:
    db:
      image: mysql:5.7
      environment:
        MYSQL_ROOT_PASSWORD: wordpress
        MYSQL_DATABASE: wordpress
        MYSQL_USER: wordpress
        MYSQL_PASSWORD: wordpress
      volumes:
        - db_data:/var/lib/mysql
    wordpress:
      depends_on:
        - db
      image: wordpress:latest
      ports:
        - "8000:80"
      environment:
        WORDPRESS_DB_HOST: db:3306
        WORDPRESS_DB_USER: wordpress
        WORDPRESS_DB_PASSWORD: wordpress
        WORDPRESS_DB_NAME: wordpress
  volumes:
    db_data:
  

• Start the entire stack with one command:

  docker-compose up -d
  

• Open http://localhost:8000 in a browser—you’ll be at the WordPress setup screen instantly. No manual MySQL installation, no user creation, no port conflict troubleshooting.
• When you’re done, tear everything down cleanly (no leftover config files or databases):

  docker-compose down -v
  

  Compare this to the hours it would take to set up these services manually, and the value speaks for itself.

3. Test Across Multiple Versions Without Environment Chaos #

Show how Docker makes testing against different runtime versions trivial. Let’s test the same Python app on Python 3.8, 3.9, and 3.10:

• Modify your Dockerfile to use a build argument for flexibility:

  ARG PYTHON_VERSION=3.9-slim
  FROM python:${PYTHON_VERSION}
  WORKDIR /app
  COPY app.py .
  RUN pip install pandas==1.3.5
  CMD ["python", "app.py"]
  

• Build images for each Python version:

  docker build -t demo-data-app:3.8 --build-arg PYTHON_VERSION=3.8-slim .
  docker build -t demo-data-app:3.9 --build-arg PYTHON_VERSION=3.9-slim .
  docker build -t demo-data-app:3.10 --build-arg PYTHON_VERSION=3.10-slim .
  

• Run each image to check for compatibility issues:

  docker run --rm demo-data-app:3.8
  docker run --rm demo-data-app:3.9
  docker run --rm demo-data-app:3.10
  

  No need to install multiple Python versions locally, no virtualenv juggling, no messy leftover packages. Each test runs in an isolated, clean environment.

4. Simplify CI/CD with Consistent Build Environments #

Show how Docker ensures your CI pipeline uses the exact same environment as your local machine. For example, a GitHub Actions workflow:

• Share this snippet to show how you can run tests in your Docker image instead of configuring the CI runner:

  name: Test Application
  on: [push]
  jobs:
    test:
      runs-on: ubuntu-latest
      steps:
        - uses: actions/checkout@v4
        - name: Build Docker image
          run: docker build -t test-app .
        - name: Run tests in container
          run: docker run --rm test-app python -m pytest tests/
  

  Explain that this eliminates "works locally, fails in CI" issues because the CI environment is identical to what you use on your machine. Plus, you don’t have to maintain complex CI runner configurations with dozens of dependencies.

The key here is to let the demos do the talking. Each example solves a real, annoying problem that your audience has probably faced. After walking through these, they’ll instantly grasp how Docker optimizes everything from local development to deployment.

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