Linux Server / Performance, Capacity & Containers
Compare container resource use with host limits during an incident
A container can be resource-limited while the host remains healthy, or several containers can contend for the same host resources.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
docker stats --no-streamRead the result
On an approved Docker host with authorized daemon access, this reports a current resource snapshot. Docker access is privileged and a snapshot does not show the full incident history.
Resolve and verify
Compare the affected container with configured limits, restart history and host pressure. Correct the measured application or capacity problem through the deployment owner.
Before changing production
Do not remove limits or restart every container based on one sample, and do not grant Docker access merely to simplify observation.