dasemu/remote-mcp-manager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: allow disabling per-container memory/CPU caps (CONTAINER_*=0)
All checks were successful
CI / test (push) Successful in 37s
Details

Browse Source 
Some hosts can't enforce cgroup limits for nested containers at all
(confirmed on an OpenRC-based unprivileged LXC with no systemd to
delegate cgroup controllers) — docker run fails outright trying to
write memory.max. 0 now skips requesting that cap instead of erroring
every deploy.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Darío Sevilla
2026-10-08 04:38:45 +02:00
parent 698173c79d
commit 1019672981
3 changed files with 25 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.env.example
View File

@@ -25,7 +25,10 @@ SESSION_SECRET=change-me-too
# installation env vars and bearer tokens at rest
MASTER_KEY=change-me-to-a-random-string-of-at-least-32-characters
# Resource caps applied to every installed MCP container (same limit for all, no per-installation override in V1)
# Resource caps applied to every installed MCP container (same limit for all, no per-installation
# override in V1). Set either to 0 to disable that cap — needed on hosts that can't enforce cgroup
# limits for nested containers (e.g. an unprivileged, OpenRC-based LXC with no systemd to delegate
# cgroup controllers; `docker run` fails outright there if a limit is requested).
CONTAINER_MEMORY_MB=512
CONTAINER_CPUS=1