I’m interested in improving the compatibility between youki and runc.
Here are a few areas I’d like to focus on:

CLI Command Compatibility

• The exec command in youki does not yet support some arguments available in runc, such as --preserve-fds and --ignore-paused .
• The update command seems to support only --pids-limit and -r.
• I haven’t conducted an exhaustive review, so there may be differences in other commands as well.
• One point to consider is that commands like exec are not defined in the OCI runtime-spec.
• I plan to identify and implement the missing CLI options to align more closely with runc.

Testing

• While youki already has integration tests using oci-runtime-tools test, runc has its own integration tests using bats.
• I’d like to make it possible to run these bats-based tests on youki.
• Running these tests and analyzing failures could help improve compatibility.

If the maintainers are okay with this direction, I’d like to proceed with these efforts.
This may involve creating multiple PRs or sub-issues to track the work incrementally.

Related Issue

Updated on 8/31

Known issues, as well as any new issues I create, will be tracked here.
Here is the list of issues related to this one.

• Support idmapped mount
  • Support idmapped mount #2307
• udpate command
  • impelementation of update command #147
• exec command
  • In youki, the exec command only works when the container status is Running. #3209
  • Difference between the exec command in runc and youki #3207
• run command
  • Difference between the run command in runc and youki #3208
• linux personality
  • Add Linux personality support #3199
• version command
  • youki version command #3197
• frozen cgroup
  • [Bug]: youki hangs when linux.cgroupsPath points to a frozen cgroup #3233
• support time namespace
  • support time namespace #3259
• The default filemode for device creation are different from runc’s.
  • The default filemode for device creation are different from runc’s. #3266