Fra R

> On docker swarm, to ensure that the containers talk to each other without exposing the door, a network has to be created with overlay type and has to be...

sure, here is the stack file ``` $ cat flyimg.yml version: "3.8" x-deploy: &deploy-snippet endpoint_mode: dnsrr replicas: 2 update_config: parallelism: 2 order: start-first delay: 10s failure_action: rollback monitor: 10s rollback_config:...

and the cited config file ``` $ cat config/flyimg.yml application_name: myflyimg.mydomain.it #debug debug: true #Number of days for header cache expires `max_age` header_cache_days: 365 #options separator options_separator: "," #Security: Signature...

last 48 hours of RAM usage 

last 12 hrs here in cpu 

the RAM now is lower, indeed (users are in vacation), let me find some busy day with RAM spikes

so, issues are raised by alarm from cadadviser on "memory", but I see several memory indicators:      so we probably have to ignore some of these...

in details: `memory_working_set_bytes` (which we read is the one watched by OOM killer) is this one 

@sadok-f any advice you can give us? even some links will be fine, then we'll dig and post here our feeds

for exampla now the alarm for prometheus query: ``` (container_spec_memory_limit_bytes > 0) AND (container_memory_working_set_bytes / container_spec_memory_limit_bytes * 100) > 90 ``` is on for a flyimg container: it's docker stats...