-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hotel-reservation failed to create shim task #343
Comments
I'm currently experiencing the same issue. Steps to reproduce:
Pod Description
K8s Version:
|
Access the frontend pod, run |
This solved my case as well, now all the pods are running! Thanks @abmuslim! |
I got the same error, have you solve this error @yinfangchen |
The container's startup path is /workspace, and the container startup command in the geo-deployment.yaml file is ./geo, which results in a "file not found" error. The Go-compiled executable files are located in the GOPATH/bin directory, which in my case is /go/bin. Therefore, I changed ./geo to /go/bin/geo. Additionally, I noticed that the container.image in the cloned geo-deployment.yaml file is not the service image that was built in the previous steps, so I changed it directly to the service image geo that was built earlier. |
I ran into a similar issue when deploying with the helm charts, with an added issue wherein the configMaps weren't being set. Here is an example from Before:
After:
Whatever default paths they were using for command and for mountPath do not seem to be working for me. For anyone else running into this issue, be sure to update this for all of the services that are failing. |
That was it! Thank you so much <3 |
I got the following error from the events when deploying the hotel-reservation:
Normal Created 1s (x2 over 3s) kubelet Created container hotel-reserv-frontend │ Warning Failed 1s (x2 over 3s) kubelet Error: failed to start container "hotel-reserv-frontend": 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: "./frontend": stat ./frontend: no such file or directory: unknown
This error appears in every service: fontend, geo, profile, rate, recommendation, reservation, search, user.
The text was updated successfully, but these errors were encountered: