3 years ago

Category: Kubernetes

In fact, there is another way to debug a process inside a container, without breaking the content structure of the container or installing any toolkit in it.

In this way, we can view the processes and network namespaces in the original container through the container we use to debug, which has everything we need installed in it.

To see the network namespaces within the original container, we need to set a few more options and run the following command to restart the debug container.

The key to being able to debug a container environment without installing extra tools in it is to run another container and have it share the PID/network namespaces with the original container.