CI runtime exec failed: exec failed: container_linux.go:349: starting container . . .

Kubernetes
#1

Dhanuj Sirohi:
CI runtime exec failed: exec failed: container_linux.go:349: starting container process caused “exec: “/root/curl-test.sh”: stat /root/curl-test.sh: no such file or directory”: unknown
command terminated with exit code 126

#2

Tej_Singh_Rana:
If a file is not available in the path, that means we’re doing something wrong so we can read the question again.
You can run the ls command to check the files availability. In a terminal or inside a pod.