Public bug reported:
Hi,
I do have an Ubuntu server with LXD virtual machines, and in one of this
virtual machines running docker. It worked for years stable and
reliably.
Since latest update (a few days ago) I can't start my docker containers
anymore:
# docker start 3262abbe7297
Error response from daemon: failed to create task for container: failed to
create shim task: OCI runtime create failed: runc create failed: unable to
start container process: error during container init: open sysctl
net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied:
unknown
Error: failed to start containers: 3262abbe7297
There's similar reports from Debian and Proxmox, and allegedly a new version of
runc triggers apparmor due to some implementation flaw.
Same with podman:
# podman run --rm -it alpine sh
Error: runc: runc create failed: unable to start container process: error
during container init: open sysctl net.ipv4.ping_group_range file: reopen fd 3:
permission denied: OCI permission denied
regards
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: runc 1.3.3-0ubuntu1~24.04.2
ProcVersionSignature: Ubuntu 6.8.0-87.88-generic 6.8.12
Uname: Linux 6.8.0-87-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CloudBuildName: server
CloudSerial: 20180426.2
Date: Mon Nov 10 01:29:09 2025
SourcePackage: runc-app
UpgradeStatus: Upgraded to noble on 2024-07-15 (482 days ago)
** Affects: runc-app (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cloud-image noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2131008
Title:
runcopen sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8:
permission denied:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc-app/+bug/2131008/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
