Need Assistance: Troubleshooting "OCI runtime create failed" error when deploying 'e2e-test-images/agnhost' via "Hello Minikube" tutorial on Windows about website HOT 11 CLOSED

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from website.

Page mentioned in issue (based on the issue title): https://kubernetes.io/docs/tutorials/hello-minikube/
/language en

from website.

This seems more like a question for minikube than an issue with the website.

I would guess it has to do with your setup running on Windows, but I'm not sure what to recommend for debugging that setup.

from website.

/retitle Need Assistance: Troubleshooting "OCI runtime create failed" error when deploying 'e2e-test-images/agnhost' via "Hello Minikube" tutorial on Windows

from website.

Looks like a support request in its current form.
/kind support

from website.

I could create deployment.
I used the following command:
kubectl create deployment hello-minikube --image=kicbase/echo-server:1.0 (from section 4).
Maybe the problem is related to image which is described in the tutorial?

from website.

The issue seems to occur when you're passing commands and arguments to the kubectl create deployment command on Windows.
kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.39 -- /agnhost netexec --http-port=8080

Could you retrieve the manifest of your deployment by running the following command?
kubectl get deployments.apps hello-node -o yaml

Please check what is present under this section (I have pasted the output I receive on MacOS)

    spec:
      containers:
      - command:
        - /agnhost
        - netexec
        - --http-port=8080
        image: registry.k8s.io/e2e-test-images/agnhost:2.39

Please check if it is adding the C:/Program Files/Git/ in the command for the container.

from website.

Yes, the line C:/Program Files/Git/agnhost exists in command section.

- command:
      - C:/Program Files/Git/agnhost
      - netexec
      - --http-port=8080
      image: registry.k8s.io/e2e-test-images/agnhost:2.39
      imagePullPolicy: IfNotPresent

in status section I have the following:

status:
  conditions:
  - lastTransitionTime: "2024-05-08T09:02:08Z"
    lastUpdateTime: "2024-05-08T09:02:08Z"
    message: Deployment does not have minimum availability.
    reason: MinimumReplicasUnavailable
    status: "False"
    type: Available
  - lastTransitionTime: "2024-05-08T09:02:08Z"
    lastUpdateTime: "2024-05-08T09:02:08Z"
    message: ReplicaSet "hello-node-fb6d66547" is progressing.
    reason: ReplicaSetUpdated
    status: "True"
    type: Progressing
  observedGeneration: 1
  replicas: 1
  unavailableReplicas: 1
  updatedReplicas: 1

The problem is related to permissions, right?

from website.

@SergeiPavlitz
I am thinking that this could be a bug in the kubectl client library for Windows.

The deployment is created using an imperative command through kubectl along with passing the commands to the container from the command line. The container command in the actual deployment manifest which is created has an unnecessary Windows specific path (C:/Program Files/Git) which obviously will not work within the container.

I would suggest to raise an issue to kubectl to get an opinion on it.
https://github.com/kubernetes/kubectl/issues

from website.

Thank you. A new issue is created.

from website.

The new issue it created

from website.