search

rancher-sandbox / rancher-desktop

Container Management and Kubernetes on the Desktop
https://rancherdesktop.io
Apache License 2.0
5.93k stars 280 forks source link

Container dashboard fails to restart an exited clusterip container after restarting VM #5873

Open IsaSih opened 11 months ago

IsaSih commented 11 months ago

Actual Behavior

Container dashboard fails to restart an exited container previously created after restarting VM

Steps to Reproduce

  1. Start Rancher Desktop
  2. Deploy kubernetes service and a container 
    kubectl create deployment nginx-test --image=nginx:stable
kubectl create service clusterip nginx-test --tcp=5000:80
  3. Via Container dashboard, stop both
  4. Restart the VM, by enabling socket-vmnet via the Preferences dialog.
  5. Wait for the application to start completely and then launch the container dashboard
  6. Try to restart the service by hitting the Start button

Result

Kubernetes creates 2 new processes as expected, however, the exited containers still are shown in the dashboard and the service cannot be restarted once the user hits the Start button via UI, and Rancher Desktop displays an error dialog.

Screenshot 2023-10-30 at 3 24 36 PM

Logs: Archive.zip

Expected Behavior

To be discussed if they should be omitted from the dashboard or the Start button should be disabled.

Additional Information

No response

Rancher Desktop Version

1.10.0-566-g9034e36d

Rancher Desktop K8s Version

1.27.6

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

macOS Ventura 13.5.2

What CPU architecture are you using?

arm64 (Apple Silicon)

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

IsaSih commented 11 months ago

The pod can be restarted successfully. Error occurs only with the service. Only successful action for the service is Delete