-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Wait for the CRI socket to be created properly #10356
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
Conversation
Before returning the container runtime back to the caller. Wait for a minute (usually 1 second) Note that this doesn't apply to the dockershim, it only replies to runtimes that are using CRI.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/ok-to-test |
|
kvm2 Driver Times for Minikube (PR 10356): 67.0s 64.4s 67.5s Averages Time Per Log docker Driver Times for Minikube (PR 10356): 26.7s 25.5s 25.6s Averages Time Per Log |
Before returning the container runtime back to
the caller. Wait for a minute (usually 1 second)
Note that this doesn't apply to the dockershim,
it only replies to runtimes that are using CRI.
The
systemctl restart containerdcompletes right away, before the service is up and running properly.This makes all
crictlfail, later on. Instead wait for the CRI socket to get created, before continuing to use it.Sample output, after this fix:
It can be an issue for large installations, where it takes a while to start up the container runtime.
Note that this doesn't apply to Docker, it only applies to CRI and not to the kubelet dockershim.
EDIT: Actually it will apply to Docker too in the future, when it starts using CRI: #9868
Closes #10355