Limit IOPS with --device-write-bps
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Hello. I am using Sysbox 0.5.2 with Docker 20.10.12.
I am trying to limit iops with command, my default runtime set as sysbox-runc.
First I run docker run -it --rm --device-write-bps /dev/vda:10mb ubuntu /bin/bash.
Then I run a command in the container:
time dd if=/dev/zero of=test.out bs=1M count=1024 oflag=direct
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 14.7389 s, 72.9 MB/s
real 0m14.740s
user 0m0.015s
sys 0m0.281s
Looks like it didn't get my instructions for limiting I/O.
Can I restrict i/o with sysbox?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported docker run command with Sysbox 0.5.2 and Docker 20.10.12, then compare the dd throughput with and without --device-write-bps. Done means determining whether Sysbox supports this I/O restriction and documenting or correcting the behavior based on that result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100