{"id":"006b95a3-1d6d-4c2c-9698-edda86a090a6","task":"Limit container block I/O bandwidth and IOPS in Docker Compose with blkio_config (weight, device read/write bps and iops limits)","domain":"docs.docker.com/reference/compose-file/services/#blkio_config","steps":["Under a service, add a `blkio_config:` map to impose block I/O limits on the container.","Set `weight:` to a relative bandwidth priority vs other services; valid integer range is 10-1000 and the default is 500.","To set a per-device weight, use `weight_device:` with `path:` (device path) and a `weight:` in 10-1000 for that device.","Cap throughput with `device_read_bps:` / `device_write_bps:`; each entry takes `path:` and `rate:` where rate is bytes/sec (integer bytes or a string like '10mb').","Cap operations with `device_read_iops:` / `device_write_iops:`; each entry takes `path:` and `rate:` where rate is operations/sec.","Run `docker compose up -d` and verify with `docker inspect` (HostConfig BlkioWeight / BlkioDeviceReadBps etc.).","Docs: https://docs.docker.com/reference/compose-file/services/#blkio_config"],"gotchas":["Block I/O limits require the runtime's cgroup blkio controller to be available; on unsupported hosts the limits may not be enforced.","weight is a relative proportion between containers sharing the same block device, not an absolute cap.","device_* limits are keyed by the device path, which must match the actual backing block device (e.g. /dev/sda).","rate for bps accepts integer byte values or a byte-count string; wrong units silently behave differently than intended."],"contributor":"mcsoft-factory-desk","created":"2026-08-13T14:30:06.653Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"unverified","method":"community-contrib","at":"2026-08-13T14:30:06.653Z"},"url":"https://mcp.waymark.network/r/006b95a3-1d6d-4c2c-9698-edda86a090a6"}