修改项目文件后构建Docker镜像未生效，如何调整Dockerfile？

Great question—this is a super common pitfall with official Dockerfiles that prioritize remote Git repos over local code! Let’s break this down clearly:

Is Docker always pulling from Git during builds? #

Absolutely not. The issue here is specific to the official Dockerfile you’re using, not Docker itself. That Dockerfile likely includes a step like RUN git clone <repo-url> that pulls the framework’s code directly from Git during the build process. This either:

• Overwrites any local files you might have copied earlier, or
• Doesn’t copy local files at all, relying entirely on the cloned Git content.

So it’s not a Docker rule—it’s just how the official build was configured.

How to Modify the Dockerfile to Use Your Local Changes #

Here’s a step-by-step fix to redirect the build to use your modified local files instead:

1. Remove or comment out Git-based code fetching #

First, scan the Dockerfile for any commands that pull code from Git. Common examples include:

• RUN git clone https://github.com/official/framework.git /app
• RUN git checkout <tag/branch> (used after cloning)

Comment out or delete these lines. For example, if your original Dockerfile has:

RUN git clone https://github.com/official/my-framework.git /app

Change it to:

# RUN git clone https://github.com/official/my-framework.git /app

2. Add a COPY command to bring in your local files #

Next, add a COPY instruction to copy your modified local project files into the Docker image’s working directory. If your local code is in the same folder as the Dockerfile, and the image’s working directory is /app, add this line:

COPY . /app

Pro tip: Double-check your .dockerignore file! Make sure it’s not ignoring critical files you modified (like source code or config files). You should ignore things like .git, node_modules, venv, or log files—stuff that doesn’t belong in the image.

3. Verify and adjust build/setup steps #

Most official Dockerfiles include steps to install dependencies (like RUN npm install or RUN pip install -r requirements.txt) after fetching code. These should still work perfectly with your local files, as long as your modified code includes the necessary dependency config files (e.g., package.json, requirements.txt).

Example: Modified Dockerfile #

Let’s say the original official Dockerfile looks like this:

FROM node:18-alpine
WORKDIR /app
RUN git clone https://github.com/official/node-framework.git .
RUN npm install
CMD ["npm", "start"]

Your modified version would be:

FROM node:18-alpine
WORKDIR /app
# Removed Git clone step
# RUN git clone https://github.com/official/node-framework.git .
# Copy local code into the image
COPY . /app
RUN npm install
CMD ["npm", "start"]

Final Build Command #

Make sure you run the build from the root of your local project directory (where your modified files and Dockerfile live):

docker build -t my-custom-framework .

This will build an image using your local changes instead of pulling from the remote Git repo.

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