Kubernetes Cannot Exec Pod

Question

Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "0acebb686c1b464e7219419ce1e15439e28aaaa2ef84392f73ffb077a9cc3c8b": OCI runtime exec failed: exec failed: container_linux.go:367: starting container process caused: exec: "cmd": executable file not found in $PATH: unknown

enter image description here

Please share some more details. What is the actual scenario and (as already mentioned above) which exact command have you used? — Wytrzymały Wiktor, Mar 30 '21 at 12:08

score 5 · Accepted Answer · answered Mar 30 '21 at 15:54

5

Unfortunately, I don't think kubernetes-metrics-scraper pod has a shell.

It's expected behaviour so it doesn't indicate that there is an issue with it from info that you've provided (if you are accessing to solve something).

You can get more details by checking if pod is in Running state, its logs in dashboard or describing a pod.

Some pods can be accessed by passing these commands: sh, /bin/sh, bash or /bin/bash, but it's not the case specifically for kubernetes-metrics-scraper.

answered Mar 30 '21 at 15:54

laimison

1,409
3
17
39

Thank you very much, I think all containers have their own shell – Iwan Setiawan Mar 31 '21 at 07:45
I had the same issue. `kubectl exec --stdin --tty myPodName -- /bin/bash` did not work. Fortunately `kubectl exec --stdin --tty myPodName -- sh` solved the issue immediately :D – d.braun1991 Apr 08 '22 at 08:19
for me, it sh with nothing – karlos Jan 12 '23 at 09:41

score 0 · Answer 2 · answered Mar 13 '23 at 16:07

0

kubectl exec --stdin --tty myPodName -- sh

As commented above, it's worked for me.

answered Mar 13 '23 at 16:07

Ravi Pullagurla

466
4
10

Kubernetes Cannot Exec Pod

2 Answers2