You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
REGRESSION: 1.35.0 exits with an error (82) and "Unable to stop VM: docker container inspect full-smoke --format=\u003cno value\u003e: exit status 1" when stopping profile with non-existing container
#20302
Open
arcivanov opened this issue
Jan 21, 2025
· 0 comments
This is a regression from 1.34.0.
The expected behavior is that stopping profile for a container that no longer/not yet exists is not an error and happens as quickly as stopping a stopped container.
$ ./minikube -p full-smoke logs --file=log.txt
❌ Exiting due to GUEST_STATUS: Unable to get control-plane node full-smoke host status: state: unknown state "full-smoke": docker container inspect full-smoke --format={{.State.Status}}: exit status 1
stdout:
stderr:
Error response from daemon: No such container: full-smoke
$ ./minikube '-p''full-smoke''stop' -o json
{"specversion":"1.0","id":"c6542a4e-b5e8-43f6-83b3-5123b6cbc1eb","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"0","message":"Stopping node \"full-smoke\" ...","name":"Stopping","totalsteps":"2"}}
{"specversion":"1.0","id":"d6994dbd-c39f-41fb-8453-e529c29032f2","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"2","message":"1 node stopped.","name":"Done","totalsteps":"2"}}
$ docker container prune
WARNING! This will remove all stopped containers.
Are you sure you want to continue? [y/N] y
Deleted Containers:
cdb6c736a17667931525463442a5304296a2f23086739febed185ad0e96215a7
7baaa8a34c212f75e8f6241b25557e54402bb40255e713d42d332763621d9406
4d2a01c36a190b0938e4660ec0c3cb23b31c211ccb2267b4cd3f2ddbba31b8fe
$ ./minikube '-p''full-smoke''stop' -o json
{"specversion":"1.0","id":"57e8b7c0-2347-4f8d-bada-a43d5222590e","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"0","message":"Stopping node \"full-smoke\" ...","name":"Stopping","totalsteps":"2"}}
{"specversion":"1.0","id":"5b2956a5-f0f6-4984-a7ec-497cc8452ce5","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"0","message":"Stopping node \"full-smoke\" ...","name":"Stopping","totalsteps":"2"}}
{"specversion":"1.0","id":"9cba94d5-5ba3-40f5-a22f-dd137d454e18","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"0","message":"Stopping node \"full-smoke\" ...","name":"Stopping","totalsteps":"2"}}
{"specversion":"1.0","id":"d323a076-eabb-47e4-bd7b-76e3f16eecbb","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"0","message":"Stopping node \"full-smoke\" ...","name":"Stopping","totalsteps":"2"}}
{"specversion":"1.0","id":"8ace8cb1-85c7-4edf-b08b-422e16c2ef39","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"0","message":"Stopping node \"full-smoke\" ...","name":"Stopping","totalsteps":"2"}}
{"specversion":"1.0","id":"b6068a63-fc2b-408f-852c-f3aeda1873fd","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.step","datacontenttype":"application/json","data":{"currentstep":"0","message":"Stopping node \"full-smoke\" ...","name":"Stopping","totalsteps":"2"}}
{"specversion":"1.0","id":"c118d8ae-8730-486d-bc95-bea44144e1fc","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.error","datacontenttype":"application/json","data":{"advice":"","exitcode":"82","issues":"","message":"Unable to stop VM: docker container inspect full-smoke --format=\u003cno value\u003e: exit status 1\nstdout:\n\n\nstderr:\nError response from daemon: No such container: full-smoke","name":"GUEST_STOP_TIMEOUT","url":""}}
{"specversion":"1.0","id":"3e3889a4-11a4-4788-bde2-ebef0bd46b0b","source":"https://minikube.sigs.k8s.io/","type":"io.k8s.sigs.minikube.error","datacontenttype":"application/json","data":{"message":"\u001b[31m╭───────────────────────────────────────────────────────────────────────────────────────────╮\u001b[0m\n\u001b[31m│\u001b[0m \u001b[31m│\u001b[0m\n\u001b[31m│\u001b[0m If the above advice does not help, please let us know: \u001b[31m│\u001b[0m\n\u001b[31m│\u001b[0m https://github.com/kubernetes/minikube/issues/new/choose \u001b[31m│\u001b[0m\n\u001b[31m│\u001b[0m \u001b[31m│\u001b[0m\n\u001b[31m│\u001b[0m Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. \u001b[31m│\u001b[0m\n\u001b[31m│\u001b[0m Please also attach the following file to the GitHub issue: \u001b[31m│\u001b[0m\n\u001b[31m│\u001b[0m - /tmp/minikube_stop_392d952f0422f1d8bbad4bfd0c98640a31c7f8a5_0.log \u001b[31m│\u001b[0m\n\u001b[31m│\u001b[0m \u001b[31m│\u001b[0m\n\u001b[31m╰───────────────────────────────────────────────────────────────────────────────────────────╯\u001b[0m"}}
$ echo$?
82
Operating System
Redhat/Fedora
Driver
Docker
The text was updated successfully, but these errors were encountered:
What Happened?
This is a regression from 1.34.0.
The expected behavior is that stopping profile for a container that no longer/not yet exists is not an error and happens as quickly as stopping a stopped container.
Attach the log file
Logs cannot be obtained either:
Operating System
Redhat/Fedora
Driver
Docker
The text was updated successfully, but these errors were encountered: