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

[SergeiPavlitz]

11h Warning Failed pod/hello-node-7c7b95ff98-phftk Error: failed to start container "agnhost": Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "C:/Program Files/Git/agnhost": stat C:/Program Files/Git/agnhost: no such file or directory: unknown

I get this error, when I try to create a deployment (link for instructions).

Steps to reproduce:

1. minikube start --driver=docker
2. in other terminal minikube dashboard --url
3. in the first terminal kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.39 -- /agnhost netexec --http-port=8080 (regarding instructions)

My OS: Windows 10 home. I use docker driver, because Hyper-V doesn't exist in windows 10 home.

Could you explain please, how to fix the issue.

[k8s-ci-robot]

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.

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-sigs/prow repository.

[dipesh-rawat]

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

[stmcginnis]

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.

[dipesh-rawat]

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

[dipesh-rawat]

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

[SergeiPavlitz]

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?

[adityasamant25]

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.

[SergeiPavlitz]

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?

[adityasamant25]

@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

[SergeiPavlitz]

Thank you. A new issue is created.

[SergeiPavlitz]

The new issue it created