Error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied: unknown

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.9
  • Operating system and version (e.g., Ubuntu 24.04):
    • debian (lxc container on proxmox host)
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • after upgrading container
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • aio

Summary of the issue you are facing:

When starting the mastercontainer, I get the error `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`

2 Likes

See https://www.reddit.com/r/docker/comments/1op6e1a/impossible_to_run_docker/

Had the same problem after upgrading my proxmox lxc containers today
and I can confirm that 
apt install containerd.io=1.7.28-1~ubuntu.24.04~noble
fixed the problem for me. Get your OS specific list with: 
apt list -a containerd.io
3 Likes

I had the same problem this morning.

I confirm @jo-me ‘s solution works.

Thank you!

Anyone having the same problem with 22.04?

# apt list containerd.io

Listing… Donecontainerd.io/jammy,now 1.7.29-1~ubuntu.22.04~jammy amd64 [installed]
apt install containerd.io=1.7.28-1~ubuntu.22.04~jammy

this forced the version back to 1.7.28-1 and solved my issue

The following does the trick for me on Debian trixie:

apt install containerd.io=1.7.28-1~debian.13~trixie

Link to the upstream bug: