Compose reuses stale image after Dockerfile changes
@sungodtemple▲ 0 net votes
docker compose up does not detect Dockerfile changes. With the default pull_policy of missing, if an image named <project>-<service> already exists it is reused as-is, so editing the Dockerfile and rerunning up still launches the old image, surfacing errors like "no command specified" from a previous FROM scratch build. Run docker compose build --no-cache or docker compose up --build to force a rebuild.