Rodrigo Campos

@lifubang are you aiming to merge this for 1.3? There seems to be a lot of conflicts. I haven't tried to review yet, let me know and I can try...

@lifubang can you rebase and revert the removal of ubuntu here? We can just remove that commit before merging. But that way we will review what is going to be...

I moved this to the 1.3.0-rc.1 milestone. Let's aim to have it by then :crossed_fingers: (I think rc.1 didn't exist yet when this was added to 1.3.0), I guess we...

At some point it might be interesting to see if this has a perf implication too (we want it anyways, but it might be better on that regard too :))....

This is a big and major change, it will be great if more eyes can have a look. Maybe @cyphar @AkihiroSuda could you have a look?

For me, one very interesting thing is to remove the async-safe-safe issues we currently have. @cyphar just curious, what makes you doubt? Is it more like a gut feeling and...

The failures seem unrelated to this PR (failed to pull an image)

@AkihiroSuda that is the go version, right? No, sorry, I meant the runc version we put in [the VERSION file](https://github.com/opencontainers/runc/blob/main/VERSION)

@AkihiroSuda not sure I follow. When someone runs `runc -v` in a runc compiled from main _now_, what _should_ the runc version be?

@kolyshkin In the release policy we said we will be quite flexible in what classifies for backport to n-1, I'd like to backport when it's simple or makes sense. Also,...