Address SQA bug: OpenPI policy runner runs in the Arena container.

[alexmillane]

Summary

Address issue that the OpenPI docs did not state that the policy runner must be run from inside the Arena container.

Detailed description

• Terminal 2 of the OpenPI quickstart now says to enter the Arena container with ./docker/run_docker.sh, matching the wording already used on the DreamZero page.
• Addresses 6491128

[greptile-apps]

Greptile Summary

This PR clarifies where to run the OpenPI policy runner.

• Instructs users to enter the Arena container with ./docker/run_docker.sh in Terminal 2.
• Keeps the policy-runner command sequence unchanged.

Confidence Score: 5/5

The documentation-only clarification is safe to merge.

The change adds the required container-entry instruction without altering commands, code, configuration, or runtime behavior.

Important Files Changed

Filename	Overview
docs/pages/quickstart/first_experiments/running_a_real_policy/openpi.rst	Clarifies that the OpenPI policy runner must be launched from inside the Arena container.

_{Reviews (1): Last reviewed commit: "Address SQA bug: state that the OpenPI p..." | Re-trigger Greptile}

[arena-review-bot]

🤖 Isaac Lab-Arena Review Bot

Summary

This is a one-line docs fix to the OpenPI quickstart: Terminal 2 now tells the reader to enter the Arena container with ./docker/run_docker.sh before launching the policy runner. The wording matches the DreamZero page exactly, so the two real-policy quickstarts stay consistent. The instruction is correct — policy_runner.py needs the Arena environment — and the change is well-scoped and minimal.

Findings

None.

Verdict

Ship it.