Error: ErrImageNeverPull when Tilt mis-detects minikube
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
If Tilt misdetects minikube, you will see this error message:
[K8s EVENT: Pod podname-54d9fff45c-nrq7x (ns: default)] Container image "username/image:tilt-6275f731c7110a74" is not present with pull policy of Never
[K8s EVENT: Pod podname-54d9fff45c-nrq7x (ns: default)] Error: ErrImageNeverPull
Tilt tries hard to talk to the in-cluster minikube Docker daemon, which is much faster and safer because don't need to push/pull images and manage registry auth. But if it can't connect, it falls back to a "normal" push/pull image flow. The error message here means that parts of Tilt think it's in the first flow, and other parts of Tilt think it's in the second flow.
It's a similar problem - but a much different failure case - than the other issues we've seen with minikube cluster detection.
For an example of this, see:
https://github.com/windmilleng/tilt/issues/3079
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 comparing this failure with the related minikube cluster-detection case in issue 3079 and trace how Tilt selects its in-cluster Docker versus normal push/pull flow. Use the ErrImageNeverPull example as the failure signal; done means both parts of Tilt consistently use the same detected flow when minikube is misdetected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100