QWQyyy commented on issue #5429: URL: https://github.com/apache/openwhisk/issues/5429#issuecomment-1632131259
> Yes as the log says, the running result is "not ok". If possible, you may need to look into the container logs as well and see if there is any problem in the pod itself too. However, it seems like I'm having a hard time finding logs for containers, since containers are always created and destroyed. So I opened two console windows, one to call the function, and the other to observe the real-time container log. The result was very unfortunate, and the same result as the wsk activation command was printed. So, how should we access the container logs correctly and see what we want. I temporarily suspect that the container may not have enough memory. I have configured the container memory to be 8GB. Maybe I should give it more memory. ```bash XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX (base) root@work1:~# kubectl logs -n openwhisk wskowdev-invoker-00-5-prewarm-pythontorch XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX XXX_THE_END_OF_A_WHISK_ACTIVATION_XXX ```  I will continue to follow up with some tests, thank you for your attention. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
