nav-img
Advanced

Logging In to a Container

Scenario

If you encounter unexpected problems when using a container, you can log in to the container to debug it.

Notes and Constraints

  • When kubectl is used in CloudShell, permissions are determined by the logged-in user.
  • When using CloudShell to access a CCE cluster or container, you can open up to 15 instances concurrently.
  • The kubectl certificate in CloudShell is valid for one day. You can reset its validity period by accessing CloudShell through the CCE console.

Using kubectl

  1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
  2. Run the following command to view the created pod:

    kubectl get pod

    The example output is as follows:

    NAME READY STATUS RESTARTS AGE
    nginx-59d89cb66f-mhljr 1/1 Running 0 11m

  3. Query the container name in the pod.

    kubectl get po nginx-59d89cb66f-mhljr -o jsonpath='{range .spec.containers[*]}{.name}{end}{"\n"}'

    The example output is as follows:

    container-1

  4. Run the following command to log in to the container-1 container in the nginx-59d89cb66f-mhljr pod:

    kubectl exec -it nginx-59d89cb66f-mhljr -c container-1 -- /bin/sh

  5. To exit the container, run the exit command.