Use v3 deploy.resources.limits format for docker-compose

- Convert mem_limit/cpus to deploy.resources.limits.memory/cpus
- Use proper v3 format that KICS recognizes
- Remove KICS exceptions for CPU/Memory limits (no longer needed)
- All services now have explicit resource constraints
This commit is contained in:
Mondo Diaz
2026-01-14 19:37:12 +00:00
parent 53c1f6a1dd
commit 8065f881f3
3 changed files with 50 additions and 30 deletions

View File

@@ -44,8 +44,11 @@ services:
- no-new-privileges:true
cap_drop:
- ALL
mem_limit: 1g
cpus: 1.0
deploy:
resources:
limits:
cpus: '1.0'
memory: 1G
postgres:
image: containers.global.bsf.tools/postgres:16-alpine
@@ -70,8 +73,11 @@ services:
- no-new-privileges:true
cap_drop:
- ALL
mem_limit: 512m
cpus: 0.5
deploy:
resources:
limits:
cpus: '0.5'
memory: 512M
minio:
image: containers.global.bsf.tools/minio/minio:latest
@@ -96,8 +102,11 @@ services:
- no-new-privileges:true
cap_drop:
- ALL
mem_limit: 512m
cpus: 0.5
deploy:
resources:
limits:
cpus: '0.5'
memory: 512M
minio-init:
image: containers.global.bsf.tools/minio/mc:latest
@@ -117,8 +126,11 @@ services:
- no-new-privileges:true
cap_drop:
- ALL
mem_limit: 128m
cpus: 0.25
deploy:
resources:
limits:
cpus: '0.25'
memory: 128M
redis:
image: containers.global.bsf.tools/redis:7-alpine
@@ -139,8 +151,11 @@ services:
- no-new-privileges:true
cap_drop:
- ALL
mem_limit: 256m
cpus: 0.25
deploy:
resources:
limits:
cpus: '0.25'
memory: 256M
volumes:
postgres-data: