ubleshooting
Should I start reading the logs to identify the source of the deployment error?
Start Troubleshooting Please help me troubleshoot deployment issues for service 698a967e72d919e1a2dfcbc7 in environment 698a967e2579f38ed02c71b7. Read the logs and identify the problem.
I'll help you troubleshoot the deployment issues. Let me start by checking the service details and then examining the build and runtime logs.
getService
getDeployments I can see the service "OpenClaw" is currently in a CRASHED status. However, there are no deployments recorded yet. Let me check the runtime logs to see what's happening:
getRuntimeLogs I found the issue! The service is crashing because the OpenClaw container is exiting immediately after starting. Looking at the logs, I can see:
Problem: The container starts successfully (image pulled and container created), but then crashes with a "BackOff: Back-off restarting failed container" error. The OpenClaw CLI is displaying its help text and then exiting, which means the container has no persistent process running.
Root Cause: OpenClaw is a CLI tool, not a service that runs continuously. When deployed as a Docker container without a proper entrypoint command, it just displays the help text and exits, causing Kubernetes to keep trying to restart it.
Solution: You need to configure the service with a proper startup command. OpenClaw needs to run its gateway service to stay alive. Here are your options:
Run the OpenClaw Gateway - This is the recommended approach for a persistent service:
openclaw gateway
Run with a specific configuration - If you have a custom setup, you might use:
openclaw onboard
Would you like me to help you configure the service with the proper startup command? I can update the service configuration to run the OpenClaw gateway, which will keep the service running continuously.