starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Docker not working after updating to version 28.5.2 #1964

New Issue
Closed
opened 2026-02-05 03:06:35 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 03:06:35 +03:00
Owner
Copy Link

Originally created by @andioz on GitHub (Nov 8, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

docker

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/docker.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-15-pve)

📝 Provide a clear and concise description of the issue.

Today I ran apt update -y && apt upgrade -y inside my docker LXC, and afterwards docker could not run containers anymore.

After some experiments with different settings (for example set unprivileged=0) I could not find a solution. The only thing I can currently do is to freeze the docker version.

The new docker version is 28.5.2.

After restoring a backup, I checked the working versions:

dpkg -l | grep -E 'docker|containerd'

Output:

ii  containerd.io                 1.7.28-1~debian.12~bookworm    amd64        An open and reliable container runtime
ii  docker-buildx-plugin          0.29.1-1~debian.12~bookworm    amd64        Docker Buildx plugin extends build capabilities with BuildKit.
ii  docker-ce                     5:28.5.1-1~debian.12~bookworm  amd64        Docker: the open-source application container engine
ii  docker-ce-cli                 5:28.5.1-1~debian.12~bookworm  amd64        Docker CLI: the open-source application container engine
ii  docker-ce-rootless-extras     5:28.5.1-1~debian.12~bookworm  amd64        Rootless support for Docker.
ii  docker-compose-plugin         2.40.2-1~debian.12~bookworm    amd64        Docker Compose (V2) plugin for the Docker CLI.
ii  docker-model-plugin           0.1.44-1~debian.12~bookworm    amd64        Docker Model Runner plugin for the Docker CLI.

Then I ran this command:

apt-mark hold \
    containerd.io \
    docker-buildx-plugin \
    docker-ce \
    docker-ce-cli \
    docker-ce-rootless-extras \
    docker-compose-plugin \
    docker-model-plugin

Now apt doesn't touch the docker components. This is of course only a workaround for now to keep my system up and running. It looks like that docker changed something significant in the last update, but I'm not an expert in this...

🔄 Steps to reproduce the issue.

I tried to create a fresh LXC instance, and it didn't work out of the box, because version 28.5.2 was installed.

❌ Paste the full error output (if available).

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

🖼️ Additional context (optional).

No response

Originally created by @andioz on GitHub (Nov 8, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? docker ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/docker.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-15-pve) ### 📝 Provide a clear and concise description of the issue. Today I ran `apt update -y && apt upgrade -y` inside my docker LXC, and afterwards docker could not run containers anymore. After some experiments with different settings (for example set unprivileged=0) I could not find a solution. The only thing I can currently do is to freeze the docker version. The new docker version is 28.5.2. After restoring a backup, I checked the working versions: ```sh dpkg -l | grep -E 'docker|containerd' ``` Output: ``` ii containerd.io 1.7.28-1~debian.12~bookworm amd64 An open and reliable container runtime ii docker-buildx-plugin 0.29.1-1~debian.12~bookworm amd64 Docker Buildx plugin extends build capabilities with BuildKit. ii docker-ce 5:28.5.1-1~debian.12~bookworm amd64 Docker: the open-source application container engine ii docker-ce-cli 5:28.5.1-1~debian.12~bookworm amd64 Docker CLI: the open-source application container engine ii docker-ce-rootless-extras 5:28.5.1-1~debian.12~bookworm amd64 Rootless support for Docker. ii docker-compose-plugin 2.40.2-1~debian.12~bookworm amd64 Docker Compose (V2) plugin for the Docker CLI. ii docker-model-plugin 0.1.44-1~debian.12~bookworm amd64 Docker Model Runner plugin for the Docker CLI. ``` Then I ran this command: ```sh apt-mark hold \ containerd.io \ docker-buildx-plugin \ docker-ce \ docker-ce-cli \ docker-ce-rootless-extras \ docker-compose-plugin \ docker-model-plugin ``` Now apt doesn't touch the docker components. This is of course only a workaround for now to keep my system up and running. It looks like that docker changed something significant in the last update, but I'm not an expert in this... ### 🔄 Steps to reproduce the issue. I tried to create a fresh LXC instance, and it didn't work out of the box, because version 28.5.2 was installed. ### ❌ Paste the full error output (if available). ``` 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 ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:06:35 +03:00
OVERLORD commented 2026-02-05 03:06:42 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 8, 2025):

Duplicate of #8890

@MickLesk commented on GitHub (Nov 8, 2025): Duplicate of #8890
OVERLORD commented 2026-02-05 03:06:59 +03:00
Author
Owner
Copy Link

@andioz commented on GitHub (Nov 8, 2025):

For those who are willing to give the LXC container more priviledges, this could work (I asked chatgpt and tried it quickly on the fresh dummy container): add this settings to the container config in /etc/pve/lxc/100.conf

lxc.privileged: 1
features: nesting=1
lxc.apparmor.profile: unconfined
lxc.cap.drop =
@andioz commented on GitHub (Nov 8, 2025): For those who are willing to give the LXC container more priviledges, this could work (I asked chatgpt and tried it quickly on the fresh dummy container): add this settings to the container config in `/etc/pve/lxc/100.conf` ``` lxc.privileged: 1 features: nesting=1 lxc.apparmor.profile: unconfined lxc.cap.drop = ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1964
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?