testcontainers / testcontainers/testcontainers-node
Support a global never-pull image policy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 272
- PR merge metrics
- No merged PRs in 30d
Description
A pull policy returning false currently disables forced refreshes but still pulls missing images. CI systems that preload images cannot enforce local-only execution, including for helpers such as Ryuk.
Could we add TESTCONTAINERS_PULL_POLICY=never to use local images and fail before registry authentication or pulls if an image is unavailable? It should cover helper containers and leave defaults unchanged. This is an image-pull restriction, not general network isolation or an offline Docker build mode.
Related: #1122 addressed unnecessary registry access for existing images; this would also prohibit pulling missing images.
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 how pull policies are applied to regular and helper containers, including Ryuk, and how TESTCONTAINERS_PULL_POLICY is read. Verify the never policy prevents registry authentication and pulls when images are missing while preserving existing defaults. Done means preloaded images run locally and unavailable images fail before any pull attempt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100