2. 'docker update' command, although I would have preferred 'docker limit'. Ability to change container limits at runtime:
- CPUQuota - CpusetCpus - CpusetMems - Memory - MemorySwap - MemoryReservation - KernelMemory
This is not correct. You cannot change kernel memory limits on Linux after processes have been started (disclaimer: I've done a bunch of work with the runC code that deals with this in order to add support for the pids cgroup). You can update everything else though.
Comments
Items of particular interest to monitoring and diagnostics:
1. docker stats --all
Built-in alternative over 'docker ps -q | xargs docker stats' which takes care of dynamic additions to the list.
For consistency, it would be nice to have a similar option in the API stats call to fetch statistics for all running containers.
2. 'docker update' command, although I would have preferred 'docker limit'.
Ability to change container limits at runtime:
- CPUQuota - CpusetCpus - CpusetMems - Memory - MemorySwap - MemoryReservation - KernelMemory
With this feature in place, there is no reason to run containers without limits, at least memory limits.
3. Logging driver for Splunk
Better approach is to enhance generic drivers to be flexible enough to send logs to any logging consumer.
This is not correct. You cannot change kernel memory limits on Linux after processes have been started (disclaimer: I've done a bunch of work with the runC code that deals with this in order to add support for the pids cgroup). You can update everything else though.
Thanks. Indeed, an attempt to set kernel memory on a running container will return an error.
Great, I was just forced to change from Splunk to F ArcSight.
So happy right now.