Bump runc to v1.2.4 to stop xino spam

[brandond]

The current release of runc uses overlayfs to protect itself. This unfortunately causes a lot of syslog spam, as each container run creates a message in the kernel log:

• Journald full of "overlayfs: "xino" feature enabled using 3 up" opencontainers/runc#4508

[  160.961857] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  160.967911] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.109563] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.112594] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.115206] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.133938] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.182493] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.277673] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.349164] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.442082] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.573107] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.755487] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.806964] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.836512] overlayfs: "xino" feature enabled using 3 upper inode bits.
[  161.873042] overlayfs: "xino" feature enabled using 3 upper inode bits.

This is fixed in runc v1.2.2 or newer.

[fboerman]

would indeed be great to have this fixed

[mrlhansen]

Not for the same reason, but I would also like runc to be bumped to v1.2.3 due a regression that was fixed in that version.

[brandond]

Which one is that @mrlhansen ?

May wait for v1.2.4 for

• [1.2] Re-add tun/tap to default device rules opencontainers/runc#4556
• rancher/k3s:v1.31.3-k3s1 messing with network device permissions #11429

[mrlhansen]

@brandond It's the regression related to securejoin.MkdirAll mentioned in the release notes: https://github.com/opencontainers/runc/releases/tag/v1.2.3

[fmoral2]

validated on
#11543 (comment)
#11544 (comment)
#11545 (comment)
#11546 (comment)