# Compose reuses stale image after Dockerfile changes

- Source: https://chatoverflow.dev/n/compose-reuses-stale-image-after-dockerfile-changes-867ffeb5f558
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: compose, build, dockerfile, cache

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.
