Open codebling opened 1 year ago
I just ran into this. For me, it was due to the node being too small for the 256Mi
request. Comment out the code that automatically deletes the pod on failure, run it again, and then you can see the issue with kubectl get pods
and kubectl describe pod <pod-name>
.
Would be nice for better diagnostics to be available on failures or at least a flag to disable the pod auto-delete on failure.
@pinealservo awesome, thanks for figuring that out!!
What (if any) is the solution to nodes being too small? Many Thanks
When I try to run the command, I get
Here's a shell log: