如何自动化同步Makefile与Dockerfile依赖，实现构建系统DRY？

Great question! Manually updating dockerfile_deps every time you add a new COPYed file to your Dockerfile is exactly the kind of repetitive, error-prone task we want to eliminate with DRY principles. Here's a straightforward, automated solution that pulls dependencies directly from your Dockerfile:

Solution 1: Dynamically Extract COPY Dependencies #

Instead of hardcoding dockerfile_deps, use a shell command inside your Makefile to automatically extract all source files referenced in COPY directives. This way, any new files you add to COPY in Dockerfile will be picked up by Makefile automatically.

Basic Implementation (Single File COPY) #

If your COPY lines only reference one file at a time (like COPY dep1 .), use this Makefile:

# Automatically pull all COPY source files from Dockerfile
dockerfile_deps := $(shell awk '/^COPY/ {print $$2}' Dockerfile)

docker_img: Dockerfile $(dockerfile_deps)
	docker image build -t my_image .
	touch "$@"

Handle Multi-File COPY Lines #

If you have COPY commands with multiple source files (like COPY dep1 dep2 .), adjust the extraction command to grab all source files (excluding the final destination .):

# Extract all source files from COPY lines (ignores the destination)
dockerfile_deps := $(shell awk '/^COPY/ {for (i=2; i<NF; i++) print $$i}' Dockerfile)

docker_img: Dockerfile $(dockerfile_deps)
	docker image build -t my_image .
	touch "$@"

How It Works #

• The awk command scans your Dockerfile for lines starting with COPY.
• For each matching line, it extracts the relevant source file(s) (skipping the destination path, which is usually . in your case).
• The dockerfile_deps variable is populated dynamically, so you never have to edit it manually again.

Bonus: Leverage Docker BuildKit (Optional) #

While the above fixes the Makefile DRY issue, you can also enable Docker BuildKit to optimize build caching further. BuildKit automatically detects changes in files used during builds, but combining it with the automated Makefile dependency tracking ensures you only trigger builds when truly necessary. To enable BuildKit, add this to your shell environment or Makefile:

export DOCKER_BUILDKIT=1

This setup keeps your build pipeline clean, maintainable, and free of manual dependency updates.

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