[Doc] Update docker install guide

[pan-x-c]

Description

As the title says

Checklist

Please check the following items before code is ready to be reviewed.

• Code has passed all tests
• Docstrings have been added/updated in Google Style
• Documentation has been updated
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @pan-x-c, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly updates the Trinity-RFT installation documentation in both English and Chinese. The primary goal is to improve clarity and guidance for users, particularly by enhancing the Docker installation process. The changes introduce explicit recommendations for different installation methods based on user experience and provide a more comprehensive, step-by-step guide for utilizing the pre-built Docker image, ensuring a smoother setup experience for new users.

Highlights

• Installation Method Recommendations: The documentation now explicitly recommends 'source' for experienced users and 'Docker' for beginners, clarifying the target audience for each method.
• Enhanced Docker Installation Guide: Detailed instructions have been added for pulling and running the Trinity-RFT Docker image directly from the GitHub Container Registry, including specific docker run commands.
• Docker Environment Usage Notes: A new note explains how to activate the uv managed Python virtual environment within the Docker container and how to install additional packages.
• Documentation Structure Reordering: The order of installation methods (Source, Docker, PyPI) has been adjusted in both English and Chinese documentation to reflect the new recommendations, with Docker now appearing before PyPI.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/docker.yaml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the installation documentation, focusing on improving the Docker installation guide in both English and Chinese. The changes successfully restructure the content to be more user-friendly by recommending installation paths based on experience. However, I've identified a couple of critical issues in the new Docker instructions: the docker run command uses an incorrect image name, and the instructions for activating the virtual environment are misleading. Additionally, there are some minor punctuation inconsistencies in the Chinese documentation. I've provided specific suggestions to address these points to ensure the documentation is accurate and clear for users.