-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Wait for crictl version after the socket is up #10705
Conversation
As there are no guarantees that the CRI socket actually _works_, just because it has been made available by the container runtime.
bb57779
to
b0bdf06
Compare
/ok-to-test |
kvm2 Driver Times for Minikube (PR 10705): 71.4s 68.0s 71.4s Averages Time Per Log
docker Driver Times for Minikube (PR 10705): 27.0s 27.4s 26.9s Averages Time Per Log
|
/retest-this-please |
the tests don't look very good on docker but looks better on Containerd |
I could only see Mac errors, not sure if there was anything related ? The code doesn't actually do anything, unless running CRI if socket == "" || socket == "/var/run/dockershim.sock" {
return nil
} |
/retest-this-please |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund, medyagh 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 |
As there are no guarantees that the CRI socket actually works,
just because it has been made available by the container runtime.
Closes #10355
Now looks something like this: