-
Notifications
You must be signed in to change notification settings - Fork 53
Cannot start xgboost-operator container #93
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Im getting the same issue, any ideas @merlintang @terrytangyuan ? |
Seems like the issue might be that Line 19 in 78f8cf5
|
@terrytangyuan I tried to use docker to build the image, but the same problem appear. |
Can you show how I can deploy xgboost operator via building docker image and running it vs using the kustomize manifests as shown in the official readme? I'm also getting the same error. I'm deploying it alongside my kubeflow environment in vanilla k8s. |
@xfate123 can you check the updated version work or not ? |
@merlintang sure,my pleasure |
I am trying to deploy operator by kustomize. But looks like the pod is not running, and the status is CrashLoopBackOff.
Then look into detail by using describe command, I have following message:
Last State: Terminated
Reason: ContainerCannotRun
Message: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: "/root/manager": stat /root/manager: no such file or directory": unknown
I did some research online, but didn't get the answer I want.
Some people said this is a Windows specific problem, just use kubectl exec -it [pod_name] -c [container_name] -- ./bin/sh.
But the thing is the container is failed to be created, so cannot use kubectl exec -it command.
Kind of confused. Appreciate any help
The text was updated successfully, but these errors were encountered: