starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Containers stop and won't start after update Docker LXC #1956

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

Originally created by @m3tc0n 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?

9.0.11

📝 Provide a clear and concise description of the issue.

After updating the Docker LXC all the containers stop and won't start anymore.

See the logs.

🔄 Steps to reproduce the issue.

Start the shell of the Docker LXC > root login > apt update && apt upgrade

❌ Paste the full error output (if available).

The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Thu Oct 30 18:17:14 CET 2025 on tty1 Docker LXC Container 🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE 🖥️ OS: Debian GNU/Linux - Version: 12 🏠 Hostname: docker-1 💡 IP Address: 192.168.30.21 root@docker-1:# apt update Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:3 http://security.debian.org bookworm-security InRelease [48.0 kB] Get:4 https://download.docker.com/linux/debian bookworm InRelease [46.6 kB] Get:5 http://security.debian.org bookworm-security/main amd64 Packages [284 kB] Get:6 https://download.docker.com/linux/debian bookworm/stable amd64 Packages [51.6 kB] Fetched 486 kB in 1s (667 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 4 packages can be upgraded. Run 'apt list --upgradable' to see them. root@docker-1:# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: containerd.io docker-ce docker-ce-cli docker-ce-rootless-extras 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 74.2 MB of archives. After this operation, 190 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 https://download.docker.com/linux/debian bookworm/stable amd64 docker-ce-cli amd64 5:28.5.2-1debian.12bookworm [16.0 MB] Get:2 https://download.docker.com/linux/debian bookworm/stable amd64 containerd.io amd64 1.7.29-1debian.12bookworm [31.9 MB] Get:3 https://download.docker.com/linux/debian bookworm/stable amd64 docker-ce amd64 5:28.5.2-1debian.12bookworm [19.8 MB] Get:4 https://download.docker.com/linux/debian bookworm/stable amd64 docker-ce-rootless-extras amd64 5:28.5.2-1debian.12bookworm [6,381 kB] Fetched 74.2 MB in 1s (77.6 MB/s) Reading changelogs... Done (Reading database ... 28012 files and directories currently installed.) Preparing to unpack .../docker-ce-cli_5%3a28.5.2-1debian.12bookworm_amd64.deb ... Unpacking docker-ce-cli (5:28.5.2-1debian.12bookworm) over (5:28.5.1-1debian.12bookworm) ... Preparing to unpack .../containerd.io_1.7.29-1debian.12bookworm_amd64.deb ... Unpacking containerd.io (1.7.29-1debian.12bookworm) over (1.7.28-1debian.12bookworm) ... Preparing to unpack .../docker-ce_5%3a28.5.2-1debian.12bookworm_amd64.deb ... Unpacking docker-ce (5:28.5.2-1debian.12bookworm) over (5:28.5.1-1debian.12bookworm) ... Preparing to unpack .../docker-ce-rootless-extras_5%3a28.5.2-1debian.12bookworm_amd64.deb ... Unpacking docker-ce-rootless-extras (5:28.5.2-1debian.12bookworm) over (5:28.5.1-1debian.12bookworm) ... Setting up containerd.io (1.7.29-1debian.12bookworm) ... Setting up docker-ce-cli (5:28.5.2-1debian.12bookworm) ... Setting up docker-ce-rootless-extras (5:28.5.2-1debian.12bookworm) ... Setting up docker-ce (5:28.5.2-1debian.12bookworm) ... Processing triggers for man-db (2.11.2-2) ...

[...]

root@docker-1:~# docker start $(docker ps -aq) 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 response from daemon: cannot join network namespace of a non running container: container gluetun is exited Error response from daemon: cannot join network namespace of a non running container: container gluetun is exited 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 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 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 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 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 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 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 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 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 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 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 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: 3444f8743047, 0b75aad0cbe7, 54e9b00912c2, 088b0f6b4571, 18431a346faf, 5dcb64c8d903, 77196d030968, 665b76e973e3, 8660c2f5588b, ae938315b813, 46e52819a699, 4c6c993d2f0b, b945f04752fb, 3d8140b7cfe5, a04e8123b1c8

🖼️ Additional context (optional).

No response

Originally created by @m3tc0n 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? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. After updating the Docker LXC all the containers stop and won't start anymore. See the logs. ### 🔄 Steps to reproduce the issue. Start the shell of the Docker LXC > root login > apt update && apt upgrade ### ❌ Paste the full error output (if available). The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Thu Oct 30 18:17:14 CET 2025 on tty1 Docker LXC Container 🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE 🖥️ OS: Debian GNU/Linux - Version: 12 🏠 Hostname: docker-1 💡 IP Address: 192.168.30.21 root@docker-1:~# apt update Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:3 http://security.debian.org bookworm-security InRelease [48.0 kB] Get:4 https://download.docker.com/linux/debian bookworm InRelease [46.6 kB] Get:5 http://security.debian.org bookworm-security/main amd64 Packages [284 kB] Get:6 https://download.docker.com/linux/debian bookworm/stable amd64 Packages [51.6 kB] Fetched 486 kB in 1s (667 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 4 packages can be upgraded. Run 'apt list --upgradable' to see them. root@docker-1:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: containerd.io docker-ce docker-ce-cli docker-ce-rootless-extras 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 74.2 MB of archives. After this operation, 190 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 https://download.docker.com/linux/debian bookworm/stable amd64 docker-ce-cli amd64 5:28.5.2-1~debian.12~bookworm [16.0 MB] Get:2 https://download.docker.com/linux/debian bookworm/stable amd64 containerd.io amd64 1.7.29-1~debian.12~bookworm [31.9 MB] Get:3 https://download.docker.com/linux/debian bookworm/stable amd64 docker-ce amd64 5:28.5.2-1~debian.12~bookworm [19.8 MB] Get:4 https://download.docker.com/linux/debian bookworm/stable amd64 docker-ce-rootless-extras amd64 5:28.5.2-1~debian.12~bookworm [6,381 kB] Fetched 74.2 MB in 1s (77.6 MB/s) Reading changelogs... Done (Reading database ... 28012 files and directories currently installed.) Preparing to unpack .../docker-ce-cli_5%3a28.5.2-1~debian.12~bookworm_amd64.deb ... Unpacking docker-ce-cli (5:28.5.2-1~debian.12~bookworm) over (5:28.5.1-1~debian.12~bookworm) ... Preparing to unpack .../containerd.io_1.7.29-1~debian.12~bookworm_amd64.deb ... Unpacking containerd.io (1.7.29-1~debian.12~bookworm) over (1.7.28-1~debian.12~bookworm) ... Preparing to unpack .../docker-ce_5%3a28.5.2-1~debian.12~bookworm_amd64.deb ... Unpacking docker-ce (5:28.5.2-1~debian.12~bookworm) over (5:28.5.1-1~debian.12~bookworm) ... Preparing to unpack .../docker-ce-rootless-extras_5%3a28.5.2-1~debian.12~bookworm_amd64.deb ... Unpacking docker-ce-rootless-extras (5:28.5.2-1~debian.12~bookworm) over (5:28.5.1-1~debian.12~bookworm) ... Setting up containerd.io (1.7.29-1~debian.12~bookworm) ... Setting up docker-ce-cli (5:28.5.2-1~debian.12~bookworm) ... Setting up docker-ce-rootless-extras (5:28.5.2-1~debian.12~bookworm) ... Setting up docker-ce (5:28.5.2-1~debian.12~bookworm) ... Processing triggers for man-db (2.11.2-2) ... [...] root@docker-1:~# docker start $(docker ps -aq) 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 response from daemon: cannot join network namespace of a non running container: container gluetun is exited Error response from daemon: cannot join network namespace of a non running container: container gluetun is exited 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 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 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 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 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 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 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 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 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 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 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 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: 3444f8743047, 0b75aad0cbe7, 54e9b00912c2, 088b0f6b4571, 18431a346faf, 5dcb64c8d903, 77196d030968, 665b76e973e3, 8660c2f5588b, ae938315b813, 46e52819a699, 4c6c993d2f0b, b945f04752fb, 3d8140b7cfe5, a04e8123b1c8 ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:03:23 +03:00
OVERLORD commented 2026-02-05 03:03:36 +03:00
Author
Owner
Copy Link

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

Also experiecing this. A temporary fix seems to be removing the Linux AppArmor settings, by adding
lxc.apparmor.profile: unconfined to the end of the relevant LXC config file. However this isn't ideal, and seems like a permissions bug in a recent script update.

@Harry55494 commented on GitHub (Nov 8, 2025): Also experiecing this. A temporary fix seems to be removing the Linux AppArmor settings, by adding `lxc.apparmor.profile: unconfined` to the end of the relevant LXC config file. However this isn't ideal, and seems like a permissions bug in a recent script update.
OVERLORD commented 2026-02-05 03:03:46 +03:00
Author
Owner
Copy Link

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

No its the official docker Bug and its duplicated.

Its Not related by us.

@MickLesk commented on GitHub (Nov 8, 2025): No its the official docker Bug and its duplicated. Its Not related by us.
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#1956
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?