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

Go 1.23.2 backports golang/go#69119. Is there expectation to continue to carry https://github.com/containerd/containerd/blame/59ffbf4ce32c71c73627bf0cb3b94587677a0020/pkg/sys/unshare_linux.go#L73-L86?

Go 1.23.2 backports golang/go#69119. Is there expectation to continue to carry https://github.com/containerd/containerd/blame/59ffbf4ce32c71c73627bf0cb3b94587677a0020/pkg/sys/unshare_linux.go#L73-L86?

We can't control the version of Go that distros or other downstream consumers use, so I think we have to leave this here as those 2 versions (1.23.0 and 1.23.1) will continue to have the issue even though newer versions are fixed.