I have two questions.
(1) I added a mem_limit for my service in my docker-compose.yml. This was due to, last time I tried running this service, it ended up consuming 8GB of memory on my host, which only had 27GB to begin with, so I had to shut down the stack.
My updated docker-compose.yml contained this:
node-exporter: labels: io.rancher.scheduler.global: 'true' tty: true image: prom/node-exporter:latest stdin_open: true mem_limit: 5000000
(I originally tried this: “mem_limit: 1g” but got the error "strconv.ParseInt “1g”: invalid syntax. So then I switched to “mem_limit: 5000000” and the error message went away)
So, after I made the above update, I re-launched my stack, and started observing my node-exporter containers. They seemed to be completely ignoring the mem_limit setting. The memory usage started creeping up rapidly, from 8MB shortly after launch, to 16 MB a few minutes later, and then 86 MB about 15 minutes later. I ended up shutting down my stack.
BTW, on these hosts we are still running Docker 1.12.3
(2) I tried running “docker-compose --version” on my hosts, but it doesn’t seem to be installed. “docker” is installed, but “docker-compose” doesn’t seem to be.