[Request] Add blkio/cgroup BFQ tuning flags to container run/create
- Dominant language
- Swift
- Stars
- 49.9k
- Forks
- 1.8k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 22
Description
### Feature request
Please add block I/O tuning flags to `container run` and `container create` for cgroup/BFQ-style workload shaping.
### Compose compatibility
Docker Compose exposes this through `service.blkio_config`. Container-Compose can parse the field, but it must currently warn-skip it because apple/container has no equivalent runtime flag surface.
### Requested CLI shape
- `--blkio-weight `
- `--blkio-weight-device :`
- `--device-read-bps :`
- `--device-write-bps :`
- `--device-read-iops :`
- `--device-write-iops :`
- matching support on `container create`
The exact implementation can be constrained to what the Linux guest and host virtualization stack can support, but a first-class CLI/API surface would let compose translators pass through supported block-I/O constraints instead of silently dropping them.
Contributor guide
Research direction
Start by tracing the container run and container create entry points and the existing service.blkio_config handling in Container-Compose. Determine which requested flags the Linux guest and host virtualization stack can support, then verify that supported values reach both commands and are no longer silently dropped by Compose translation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, swift
- Domain
- cli, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100