From 5dac55405026f5c2a37d4842d1962c3bf53b893c Mon Sep 17 00:00:00 2001 From: jimmy Date: Sat, 24 Oct 2026 17:29:15 +1300 Subject: [PATCH] Drop container resource limits from compose Newer Docker Compose rejects pids_limit alongside deploy.resources.limits. Co-Authored-By: Claude Opus 5.5 --- README.md | 1 - compose.yaml | 6 ------ 2 files changed, 7 deletions(-) diff --git a/README.md b/README.md index 75b5d88..20940f8 100644 --- a/README.md +++ b/README.md @@ -54,7 +54,6 @@ Open and log in as `cashbook` with the password from - read-only container filesystem, with scratch space only in `/tmp` (tmpfs); - no Linux capabilities and `no-new-privileges`; - runs as a non-root user. -- **Limits:** 1 CPU, 1 GB of memory, 256 processes. It uses about 150 MB in practice. - **Operations:** a health check on `/healthz`, rotated logs (3 × 10 MB) and `restart: unless-stopped`. diff --git a/compose.yaml b/compose.yaml index a8be98b..3eef64f 100644 --- a/compose.yaml +++ b/compose.yaml @@ -34,12 +34,6 @@ services: - ALL security_opt: - no-new-privileges:true - pids_limit: 256 - deploy: - resources: - limits: - cpus: "1.0" - memory: 1g logging: driver: json-file