Public bug reported:
tar behaves differently between Ubuntu 24.04 (noble) and 26.04 (resolute) when
openat2 isn't supported by the running kernel (i.e. kernel < 5.6):
- On 24.04 (glibc 2.39, no native openat2 wrapper), tar uses gnulib's own
openat2() replacement, which falls back gracefully to plain openat when the
syscall returns ENOSYS. Works fine.
- On 26.04 (glibc 2.43, native openat2 wrapper), tar links directly
against glibc's openat2(), which has no fallback of its own. ENOSYS
propagates as a hard failure: tar: ./usr/bin: Cannot stat: Function not
implemented
This matters in practice when running a 26.04-based container on a host
with an older kernel - it fails, while 24.04 on the identical host works
fine. Is this a known/intended difference, or worth tracking as a bug?
** Affects: tar (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2166326
Title:
tar hard-fails with ENOSYS on kernels < 5.6 in Ubuntu 26.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2166326/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
