Logging to stdout for ray serve

Ray Serve
2

Based on the entrypoint.sh file, you seem to be starting Ray and then immediately deploying the Serve config to the new, local Ray cluster. This should be sufficient for your single-node use case. Generally, users put Serve in production using KubeRay, with a long-running Ray cluster on VMs, or on a managed Ray service like Anyscale.

There’s a couple possible ways to access logs for your setup.

  1. Use serve run: Since you’re already waiting for the deployments to start with python -m rayserve.wait, you could use serve run rayserve.deployer:deployment_graph instead of serve deploy config.yaml. serve run will block and wait for the config to deploy. Afterwards, the logs should stream back to the container console.

  2. Access them manually: Ray Serve stores all its logs in the /tmp/ray/session_latest/logs/serve/ directory on each node.

I’d recommend starting with (1) and see if it fulfills your use case.