Skip to main content

Use Webshell to Log In to an Instance

This document describes the Webshell feature of TCBR and how to use Webshell to complete basic Ops needs.

Operation Background​

A container is a transient environment for running services. When using TCBR, you only need to focus on your service and do not need to directly operate the container, including creation, configuration, update, restart, or termination. However, to facilitate online issue locating and troubleshooting, especially debugging the code, TCBR provides a simplified Webshell in the console for you to view and debug your containers.

Note

Directly operating containers via Webshell may pose risks. TCBR only provides a direct method to access containers. All operations performed in Webshell are beyond the awareness and control of TCBR.

  • If your operations in Webshell cause container OOM, it may result in service interruption.
  • If you directly modify the container configuration in Webshell, it may cause inconsistencies with the configuration recorded in TCBR, leading to confusion in subsequent operations.

Step 1: Access the Development Platform​

Enter the Development Platform and switch to the specified environment as needed.

Navigate to the Compute - CloudBase Run service.

Step 2: Access the Service Details Page​

Click the service name to go to the service details page.

Step 3: Access the Instance Details Page​

Click View Instance Details in the basic service information to open the instance details list.

Step 4: Access the Webshell Page​

Click "Webshell" corresponding to the container you need to debug to enter the Webshell management page.

Tip

Based on the replica count, scaling condition, and current traffic status of the version, there may be multiple instances (containers) under your version. All containers under the same version are created based on the version configuration, with completely consistent configuration information. Therefore, in most cases, you can select any container to enter Webshell for debugging and problem locating of the current version. However, in some special cases, only specific containers may be abnormal.

Note

If a slim container is used and there is no sh or bash tool inside the container, it will cause the shell to fail to start. You can update the base image to include shell capabilities or add shell installation in the dockerfile.

Step 5: Debugging Operations​

You can start debugging your service.