SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-06-04 06:22:08 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Docker LXC - Portainer unable to access local environment #2339

New Issue
Closed
opened 2025-11-20 05:27:40 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 05:27:40 -05:00
Owner
Copy Link

Originally created by @Stavr0 on GitHub (Nov 16, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Docker LXC

📂 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 Bookworm

📈 Which Proxmox version are you on?

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

📝 Provide a clear and concise description of the issue.

First run, after running script and applying the apparmor fix (#8890)

Initial setup of Portainer functioned normally, but I was unable to connect to 'local' enviromnent.

🔄 Steps to reproduce the issue.

Connect to portainer on LXC guest
Click on local environment

❌ Paste the full error output (if available).

Expect
Connection to local dashboard is successful
Actual
Unable to connect to environment named local

🖼️ Additional context (optional).

Workaround is to add following override
systemctl edit docker.service

Add following block

[Service]
Environment=DOCKER_MIN_API_VERSION=1.24

Restart docker daemon
systemctl restart docker.service

Originally created by @Stavr0 on GitHub (Nov 16, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Docker LXC ### 📂 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 Bookworm ### 📈 Which Proxmox version are you on? pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-16-pve) ### 📝 Provide a clear and concise description of the issue. First run, after running script *and* applying the apparmor fix (#8890) Initial setup of Portainer functioned normally, but I was unable to connect to 'local' enviromnent. ### 🔄 Steps to reproduce the issue. Connect to portainer on LXC guest Click on `local` environment ### ❌ Paste the full error output (if available). Expect Connection to `local` dashboard is successful Actual `Unable to connect to environment named local` ### 🖼️ Additional context (optional). Workaround is to add following override `systemctl edit docker.service` Add following block ``` [Service] Environment=DOCKER_MIN_API_VERSION=1.24 ``` Restart docker daemon `systemctl restart docker.service`
saavagebueno added the bug label 2025-11-20 05:27:40 -05:00
saavagebueno commented 2025-11-20 05:27:40 -05:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (Nov 16, 2025):

May not be related, but I've only recently started having the same problem.
I've been running it for years though without issue though.

Tried to build an LXC today to troubleshoot the above issue and Portainer also fails on install:

      Would you like to add Portainer (UI)? <y/N> y
  ⏳   Installing Portainer 2.33.3Unable to find image 'portainer/portainer-ce:latest' locally
latest: Pulling from portainer/portainer-ce
4f4fb700ef54: Pull complete 
9f7772ceb88a: Pull complete 
d35c85f36345: Pull complete 
f3e139b9cd66: Pull complete 
089b96337e3d: Pull complete 
2d896f38a01e: Pull complete 
22d4f45bf667: Pull complete 
c551c6af3241: Pull complete 
Digest: sha256:d38a6876b61df32e4da13c0ca61cf2aa0f27afc103abb4ca7ad4e1cf000e17c3
Status: Downloaded newer image for portainer/portainer-ce:latest
7ef1dc049cbe7c82b17d91fd5d68cf1c7353755074a2283aee68dabe0abfe075
docker: 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
@oOStroudyOo commented on GitHub (Nov 16, 2025): May not be related, but I've only recently started having the same problem. I've been running it for years though without issue though. Tried to build an LXC today to troubleshoot the above issue and Portainer also fails on install: ``` Would you like to add Portainer (UI)? <y/N> y ⏳ Installing Portainer 2.33.3Unable to find image 'portainer/portainer-ce:latest' locally latest: Pulling from portainer/portainer-ce 4f4fb700ef54: Pull complete 9f7772ceb88a: Pull complete d35c85f36345: Pull complete f3e139b9cd66: Pull complete 089b96337e3d: Pull complete 2d896f38a01e: Pull complete 22d4f45bf667: Pull complete c551c6af3241: Pull complete Digest: sha256:d38a6876b61df32e4da13c0ca61cf2aa0f27afc103abb4ca7ad4e1cf000e17c3 Status: Downloaded newer image for portainer/portainer-ce:latest 7ef1dc049cbe7c82b17d91fd5d68cf1c7353755074a2283aee68dabe0abfe075 docker: 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 ```
saavagebueno commented 2025-11-20 05:27:40 -05:00
Author
Owner
Copy Link

@Stavr0 commented on GitHub (Nov 16, 2025):

Tried to build an LXC today to troubleshoot the above issue and Portainer also fails on install ...

The solution was to tweak the AppArmor configuration as described in ticket #8890 thread. This allowed the installation script to finish successfully -- the last step was failing on Portainer deployment.

Then the API version tweak fixed the problem where Portainer could not access the docker engine.

@Stavr0 commented on GitHub (Nov 16, 2025): > _Tried to build an LXC today to troubleshoot the above issue and Portainer also fails on install ..._ The solution was to tweak the *AppArmor* configuration as described in ticket #8890 thread. This allowed the installation script to finish successfully -- the last step was failing on Portainer deployment. - https://github.com/community-scripts/ProxmoxVE/issues/8890#issuecomment-3492891975 - https://github.com/opencontainers/runc/issues/4968 Then the API version tweak fixed the problem where Portainer could not access the docker engine.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2339
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?