-
Notifications
You must be signed in to change notification settings - Fork 456
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
crictl rmi <image> doesn't works with docker #568
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
This is not a duplicate of #504
…On Tue, 19 May, 2020, 4:31 PM Mike Brown, ***@***.***> wrote:
also dup:
#504 <#504>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#568 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFZLP4RVIDGDT5MAYYYYWRTRSJRG3ANCNFSM4J644ACQ>
.
|
crictl.. sends the action to the container runtime... the container runtime returns the result of the action.. in this case the container runtime returned success for the rmi request. A force option may be more successful #504. You'll have more luck getting this addressed at the container runtime than here in the crictl tool. |
Ok, I'll check with the force option and update the results here. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I have a linux machine with docker engine and crictl. cri-tools v1.16.1. crictl by default uses
unix:///var/run/dockershim.sock
as the runtime-endpoint and successfully recognizes docker as the runtime.crictl pull jenkins
==> successfulcrictl images
==> successful. i am able to see thejenkins
imagejenkins
image usingcrictl rmi jenkins
==> command output is successfulcrictl images
==> I still see the jenkins imageSee log below:-
The text was updated successfully, but these errors were encountered: