How to dump goroutine of container entry point process?

php editor Strawberry will introduce to you how to dump the goroutine of the container entry point process. When developing containerized applications using the Go language, we often need to understand and debug running goroutines. Dumping the goroutine of the container entry point process is a common debugging method, which can help us analyze and solve problems in the application. In this article, we will discuss in detail how to use relevant tools and techniques to dump the goroutine of the container entry point process, and provide specific steps and sample code. Let’s explore this fun and practical topic together!

Question content

I have an application run by docker-compose up. When stopping the application via docker-compose stop, one of the containers does not terminate. The container runs a process written in Go, so I want to dump the goroutine of that process to see where the process is stuck.

I can docker ps view the container and then docker exec -it <container-id> bash into the container, but once I kill -QUIT <process id&gt ;, as the process terminates, the container also stops, so I cannot get the goroutine dump.

How to get the goroutine dump in this case?

Workaround

The container is also stopped, so I can't get the goroutine dump.

I think you can get goroutine dumps from the container's logs, provided:

1. docker-compose stop Stop running containers without deleting them;
2. kill -quit <process id> Dump goroutine to stderr.

   The following is the docker command to get the container log (-n specifies the number of lines to display from the end of the log):

   $ docker logs -n 1000 [container-name]

   The above is the detailed content of How to dump goroutine of container entry point process?. For more information, please follow other related articles on the PHP Chinese website!