Drop container resource limits from compose
Newer Docker Compose rejects pids_limit alongside deploy.resources.limits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9b9203c4bb
commit
5dac554050
2 files changed
-7
No files matched your search
@@ -54,7 +54,6 @@ Open <http://127.0.0.1:8765> and log in as `cashbook` with the password from
|
|||||||
- read-only container filesystem, with scratch space only in `/tmp` (tmpfs);
|
- read-only container filesystem, with scratch space only in `/tmp` (tmpfs);
|
||||||
- no Linux capabilities and `no-new-privileges`;
|
- no Linux capabilities and `no-new-privileges`;
|
||||||
- runs as a non-root user.
|
- 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
|
- **Operations:** a health check on `/healthz`, rotated logs (3 × 10 MB) and
|
||||||
`restart: unless-stopped`.
|
`restart: unless-stopped`.
|
||||||
|
|
||||||
|
|||||||
@@ -34,12 +34,6 @@ services:
|
|||||||
- ALL
|
- ALL
|
||||||
security_opt:
|
security_opt:
|
||||||
- no-new-privileges:true
|
- no-new-privileges:true
|
||||||
pids_limit: 256
|
|
||||||
deploy:
|
|
||||||
resources:
|
|
||||||
limits:
|
|
||||||
cpus: "1.0"
|
|
||||||
memory: 1g
|
|
||||||
|
|
||||||
logging:
|
logging:
|
||||||
driver: json-file
|
driver: json-file
|
||||||
|
|||||||
Reference in new issue
Block a user