Hello @strrchr, thank you for this question and welcome to the Go project!

To make this issue actionable:
a) could you please provide a sample/minimal reproducing program and how you ran it, that you used to come to this conclusion? For example, you could report that it could have been

package main

func main() {
    panic("Bye")
}

Please report the source code of what you could use to reproduce the problem.

b) Please list how you are starting the container in your Dockerfile. The step with which you passed in GOTRACEBACK when running your dockerize app might show you why it failed e.g. if you used CMD ["GOTRACEBACK=1", "./proc"] I believe this doesn't work
c) I've heard about issues with PID 1 ignoring signals unless explicitly coded to do so https://docs.docker.com/v17.12/engine/reference/run/#foreground but I am not a Docker expert
d) Do other process successfully generate the core dump and not just the PID 1 process?

Thank you!

Thank you!
Finally, I figure out that it's PID 1 problem.
When go program run as PID 1 and panic, no core dump generated.

Thank you for the confirmation that it is a PID 1 issue that's agnostic of the binary's source. Please examine how to get your binaries running as non-PID 1. I shall close this issue as the issue is related to Docker and not to Go but please don't hesitate to reach out in case of any other issues.