I thought runc was fixed to produce ENOSYS by now for unknown syscalls
to avoid that mess. We can't have every glibc update breaking containers
like this...
405 clone3({flags=CLONE_VM|CLONE_VFORK, exit_signal=SIGCHLD,
stack=0x7fc77e3d3000, stack_size=0x9000}, 88) = -1 EPERM (Operation not
permitted)
Not sure if it applies to crun, someone check with that :D
** Also affects: runc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: crun (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/1943049
Title:
Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm
-f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb
/var/cache/apt/*.bin || true'
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1943049/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
