rancher-sandbox / rancher-desktop

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

Container never reaching ready state #5435

Open grahameccleston opened 1 year ago

grahameccleston commented 1 year ago

Actual Behavior

After changing the Kubernetes version, installing any version of the oci://registry-1.docker.io/bitnamicharts/postgresql chat results in the container never reaching ready status. The Readiness check for the container uses a command within the container to check the readiness state, attempted to execute a shell in this container or any other results in

error: Internal error occurred: error executing command in container: http: invalid Host header

Believe this is a possible similar issue to #5404 as I have also tried resetting Rancher, uninstalling and unregistering WSL but the problem persists after reinstalling.

Dont know if this issue is related with the the Golang bug https://discuss.kubernetes.io/t/http-invalid-host-header-error-while-executing-a-command-in-pod/24868

Steps to Reproduce

Change Kubernetes version and deploy helm chart

Result

error: Internal error occurred: error executing command in container: http: invalid Host header

Expected Behavior

Additional Information

No response

Rancher Desktop Version

1.9.1

Rancher Desktop K8s Version

1.27.4

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10 Pro 22H2

What CPU architecture are you using?

x64

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

None

Windows User Only

N/A

grahameccleston commented 1 year ago

Chaining the container engine to containerd and restarting the cluster, the pod is initialized and the container then shows the ready status. Appears to be dockerd issue.

gunamata commented 12 months ago

@grahameccleston , I would like to try reproducing the issue on my machine. Can you please share with me the steps you followed that lead you to the problem? Thanks.

gunamata commented 12 months ago

For example, I have tried below steps with Rancher Desktop 1.10 and it works as expected.

helm repo add bitnami https://charts.bitnami.com/bitnami
helm install --wait --timeout=20m wordpress bitnami/wordpress --set=service.type=NodePort --set=volumePermissions.enabled=true --set=mariadb.volumePermissions.enabled=true
fabiorauber commented 1 week ago

Is it related to https://github.com/moby/moby/issues/45935?