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

Zot Default Settings Cause OOM #2224

New Issue
Closed
opened 2026-02-05 04:15:38 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 04:15:38 +03:00
Owner
Copy Link

Originally created by @chrismuzyn on GitHub (Dec 25, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

zot-registry.sh

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.1.2

📝 Provide a clear and concise description of the issue.

Zot appears to OOM with the default 2048MB of memory it is given. Upon launching, its single cpu seems to spin up to 100 percent. After increasing the memory to 4096, there is evidence of OOMing. It appears something using using a lot of buffer memory in this application (possibly /tmp/ filesystem). Also, it is categorized on the site as "Media", when it should probably go in "Containers & Docker".

🔄 Steps to reproduce the issue.

Run the script, watch the LXC container journalctl fill with OOM logs.

❌ Paste the full error output (if available).

root@zot-registry:~# free -h 
               total        used        free      shared  buff/cache   available
Mem:           4.0Gi       2.1Gi       1.9Gi       2.0Gi       2.0Gi       1.9Gi
Swap:             0B          0B          0B

root@zot-registry:/tmp# du -h -d 1
394M    ./getter210944328
812M    ./trivy-2350
855M    ./zot
0       ./systemd-private-d47fb394a6414ca5aa19e33a1b416a66-systemd-logind.service-qjxuh7
0       ./.font-unix
0       ./.XIM-unix
0       ./.ICE-unix
0       ./.X11-unix
2.1G    .

🖼️ Additional context (optional).

No response

Originally created by @chrismuzyn on GitHub (Dec 25, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? zot-registry.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/zot-registry.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.1.2 ### 📝 Provide a clear and concise description of the issue. Zot appears to OOM with the default 2048MB of memory it is given. Upon launching, its single cpu seems to spin up to 100 percent. After increasing the memory to 4096, there is evidence of OOMing. It appears something using using a lot of buffer memory in this application (possibly /tmp/ filesystem). Also, it is categorized on the site as "Media", when it should probably go in "Containers & Docker". ### 🔄 Steps to reproduce the issue. Run the script, watch the LXC container journalctl fill with OOM logs. ### ❌ Paste the full error output (if available). ``` root@zot-registry:~# free -h total used free shared buff/cache available Mem: 4.0Gi 2.1Gi 1.9Gi 2.0Gi 2.0Gi 1.9Gi Swap: 0B 0B 0B ``` ``` root@zot-registry:/tmp# du -h -d 1 394M ./getter210944328 812M ./trivy-2350 855M ./zot 0 ./systemd-private-d47fb394a6414ca5aa19e33a1b416a66-systemd-logind.service-qjxuh7 0 ./.font-unix 0 ./.XIM-unix 0 ./.ICE-unix 0 ./.X11-unix 2.1G . ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:15:38 +03:00
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#2224
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?