-
Notifications
You must be signed in to change notification settings - Fork 18.9k
--device-write-bps results in "no such file or directory" #44904
Copy link
Copy link
Closed
docker/cli
#3999Labels
kind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.status/0-triageversion/23.0
Description
Description
--device-write-bps and --device-read-bps are not working as expected:
# docker run -ti --device-write-bps=/dev/mapper/delayed:500mb ubuntu:22.04 /bin/bash
docker: Error response from daemon: stat 500mb: no such file or directory.
ERRO[0000] error waiting for container: context canceled
I looked with strace and I think this is the syscall that's failing:
280956 newfstatat(AT_FDCWD, "500mb", 0xc0007b4370, 0) = -1 ENOENT (No such file or directory)
--device-write-bps=/dev/mapper/delayed:500 also fails with the same error (stat 500: no such file or directory.)
--device-write-iops works:
# docker run -ti --device-write-iops=/dev/mapper/delayed:500 ubuntu:22.04 /bin/bash
root@0ac981aa0d8d:/#
Reproduce
docker run -ti --device-write-bps=/dev/mapper/delayed:500mb ubuntu:22.04 /bin/bash
Expected behavior
The container should start with the correct block I/O throttling settings.
docker version
Client: Docker Engine - Community
Version: 23.0.0
API version: 1.42
Go version: go1.19.5
Git commit: e92dd87
Built: Wed Feb 1 17:46:45 2023
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 23.0.0
API version: 1.42 (minimum version 1.12)
Go version: go1.19.5
Git commit: d7573ab
Built: Wed Feb 1 17:44:25 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.16
GitCommit: 31aa4358a36870b21a992d3ad2bef29e1d693bec
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d
docker-init:
Version: 0.19.0
GitCommit: de40ad0docker info
Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.10.2
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.15.1
Path: /usr/libexec/docker/cli-plugins/docker-compose
scan: Docker Scan (Docker Inc.)
Version: v0.23.0
Path: /usr/libexec/docker/cli-plugins/docker-scan
Server:
Containers: 22
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 31aa4358a36870b21a992d3ad2bef29e1d693bec
runc version: v1.1.4-0-g5fd4c4d
init version: de40ad0
Security Options:
seccomp
Profile: builtin
Kernel Version: 4.18.0-358.el8.x86_64
Operating System: CentOS Stream 8
OSType: linux
Architecture: x86_64
CPUs: 40
Total Memory: 187.6GiB
Name: xxx
ID: 363da9fd-b7de-447c-a6e8-f6cc1730d9e6
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: falseAdditional Info
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.status/0-triageversion/23.0