Add a way to force a build even if a cache exists
Open
Nobody has claimed this yet.
enhancement
need spec
user-feedback
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
The `--no-cache` option is not supported in the `docker compose up` command, so this might be non-trivial.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the CLI implementation of the `docker compose up` command and how it handles existing build caches. Check whether the underlying Compose invocation exposes a supported no-cache path. Done means users can explicitly force a build despite an existing cache, with the behavior covered by the relevant CLI tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, typescript
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100