nerdctl
nerdctl copied to clipboard
support print stack
I’m not sure how this is useful, as nerdctl isn’t a daemon.
Even if it is useful, the default behavior must be to propagate signals to the container.
I’m not sure how this is useful, as nerdctl isn’t a daemon.
Even if it is useful, the default behavior must be to propagate signals to the container.
because docker-cli support print stack, if nerdctl hang,I want to known where it hang ,for an example https://github.com/containerd/nerdctl/issues/1089 this issue I can't know where is hang
it may be implemented on the containerd side and enabled in nerdctl.