Add entrypoint environment variable to Docker params

[KaneOne]

The container runtime has two phases: build and start, but the environment variables passed from outside are lost during dockerStart.

What does this PR do?

The dockerStart method also needs to read environment variables, including entryfile and others.

Summary by CodeRabbit

• Chores
  • Updated Docker configuration to pass an environment variable to the container at startup.

[coderabbitai]

Walkthrough

Adds the OPEN_RUNTIMES_ENTRYPOINT environment variable to the dockerStart command invocation in the Docker emulation module. The variable is set to the value of func.entrypoint. This is a single-line addition with no changes to public signatures or control flow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically summarizes the main change: adding an entrypoint environment variable (OPEN_RUNTIMES_ENTRYPOINT) to Docker parameters in the dockerStart command.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}