This section describes how to view container details.

Note

KubeSphere only supports viewing details of running containers and does not support viewing details of stopped containers.

Prerequisites

You need to join a project and have the Application Workloads View permission in the project. For more information, see Project Members and Project Roles.

Steps

  1. Log in to the KubeSphere web console with a user who has Application Workloads View permissions and enter your workspace.

  2. Click Application Workloads > Pods in the left navigation pane.

  3. Select a project from the drop-down list in the upper left corner of the page.

  4. In the pod list, click the name of a pod to open its details page.

  5. On the pod details page, under the Resource Status tab, in the Containers section, click the name of a container to open the container details page.

  6. On the container details page, view the container’s resource attributes in the Properties section.

    Parameter Description

    Cluster

    The cluster to which the container belongs.

    Project

    The project to which the container belongs.

    Application

    The application to which the container belongs.

    Status

    The status of the container.

    • Pending: The container is performing pre-start operations, such as pulling images from the image service or reading data from Secrets.

    • Running: The container is running normally. If the container is configured with a post-start action and its status is Running, then the container’s pre-start actions have been completed.

    • Terminated: The container has ended successfully, or has ended due to some failure.

    Image

    The image used by the container.

    Image ID

    The ID of the image used by the container.

    Port

    The port of the container.

    Command

    The command executed inside the container when it starts.

    Resource Reservation

    The CPU and memory resources reserved by the system for the container.

    Resource Limit

    The upper limit of CPU and memory resources that the container can use.

    Image Pull Policy

    The image pull policy of the container.

    • IfNotPresent: When the pod is created or updated, the image file stored on the node by the container runtime is used first.

    • Always: When the pod is created or updated, an attempt is made to pull the image from the image service every time.

    • Never: When the pod is created or updated, only the image stored on the node by the container runtime is used. If the required image does not exist locally, container creation will fail.

    Restart Count

    The number of times the container has been restarted.

  7. Under the Resource Status tab, view the container’s health check configuration, the volumes mounted in the container, the mount paths of the volumes, and the access modes.

  8. Click the Environment Variables tab to view the container’s environment variables.