-
Notifications
You must be signed in to change notification settings - Fork 38.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic when pulling images fails #29129
Comments
@mikekap what version of kubelet is this? @ronnielai do you mind taking a look since you are looking at cleaning up the image puller code? Thanks! Feel free to unassign yourself for whatever reason. |
This is because we never use and set the "privilege function". This is an engine-api bug, and we should bump up the engine-api version to fix this. And I'm not sure whether this needs a cherry-pick, :P. |
IMO, this affects kubelet's reliability and should be patched to 1.3. |
@kubernetes/rh-cluster-infra |
@yujuhong I tried with 1.3.0 and 1.3.2 |
Automatic merge from submit-queue Update docker engine-api to dea108d3aa #29129
@Random-Liu @mikekap @ronnielai This issue can be closed now right? (Since the #29144 is merged already) |
This happens right after an image pull fails (in my case, due to failed auth):
This causes the pod to be forever stuck in "creating container" state.
The text was updated successfully, but these errors were encountered: