Bug report(Kubernetes: hotelReservation): Kubernetes pods fail with RunContainerError (wrong command path).

[thenovatasha]

Summary

Several services fail to start on Kubernetes. Pods show RunContainerError with exec: "./": stat ./: no such file or directory. The images place binaries under /go/bin/, but the Deployments run ./.

Affected services

frontend, geo, profile, rate, recommendation, reservation, search, user.

Environment

Platform: minikube (single node)
K8s: apps/v1 Deployments
Images: deathstarbench/hotel-reservation:latest
Source: hotelReservation/kubernetes manifests generated by Kompose

Steps to reproduce

kubectl apply -Rf hotelReservation/kubernetes

Wait for pods.

Run kubectl get pods and kubectl describe pod for any failing service.

Expected

Pods reach Running. Service endpoints are ready.

Actual

Pods stay in ContainerCreating or RunContainerError. Events include:

RunContainerError: exec: "./frontend": stat ./frontend: no such file or directory

Diagnostics

docker run --rm --entrypoint sh deathstarbench/hotel-reservation:latest -c 'which frontend || find / -maxdepth 3 -name frontend 2>/dev/null'

Output: /go/bin/frontend

Similar paths for other services: /go/bin/geo, /go/bin/profile, etc.

Root cause

Kompose output set command: ["./"]. The image installs binaries under /go/bin. The working directory in the container does not hold ./.

Workarounds confirmed

Set command: ["/go/bin/"] per Deployment or remove command: to use the image entrypoint if present.

Proposed fix (see PR)
Update Deployments call svc directly:

command: [""]
for each service listed above.