Hi @lengrongfu. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

How do you feel about using GOMOD env instead?

$ pwd
/Users/mxpv/Github/containerd/script/setup

$ go env | grep GOMOD
GOMOD="/Users/mxpv/Github/containerd/go.mod"

Documentation (go help environment):

GOMOD
The absolute path to the go.mod of the main module.
If module-aware mode is enabled, but there is no go.mod, GOMOD will be
os.DevNull ("/dev/null" on Unix-like systems, "NUL" on Windows).
If module-aware mode is disabled, GOMOD will be the empty string.

How do you feel about using GOMOD env instead?

$ pwd
/Users/mxpv/Github/containerd/script/setup

$ go env | grep GOMOD
GOMOD="/Users/mxpv/Github/containerd/go.mod"

Documentation (go help environment):

GOMOD
The absolute path to the go.mod of the main module.
If module-aware mode is enabled, but there is no go.mod, GOMOD will be
os.DevNull ("/dev/null" on Unix-like systems, "NUL" on Windows).
If module-aware mode is disabled, GOMOD will be the empty string.

First contact with GOMOD, but it feels very useful in the project.

@fuweid @thaJeztah Can you again review this PR? thanks！