Hi @zouyee. 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.

reading https://gopkg.in/yaml.v2?go-get=1: 502 Bad Gateway

@zouyee: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

server response: Cannot obtain refs from GitHub: cannot talk to GitHub: Get https://github.com/go-yaml/yaml.git/info/refs?service=git-upload-pack: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

replace direct with GOPROXY

/cc @mikebrow @AkihiroSuda @mxpv @dmcgowan

If multiple PRs are hitting the proxy issue, might be worth splitting it into a separate PR. That is a much faster review.

If multiple PRs are hitting the proxy issue, might be worth splitting it into a separate PR. That is a much faster review.

Can you rebase this on the current tip of main?

Can you rebase this on the current tip of main?

done