Skip to content
This repository was archived by the owner on May 12, 2021. It is now read-only.
This repository was archived by the owner on May 12, 2021. It is now read-only.

vCPUs not detected if cpuset fails before update the number of vCPUs #352

@devimc

Description

@devimc

Description of problem

└─ $ docker run --rm --name foo -dti debian bash
917b7fb254364fe8f4d905a18ebde4813f67c311fd9562298e885a253dc6c115
└─ $ docker update --cpuset-cpus "0-4" foo
Error response from daemon: Cannot update container 917b7fb254364fe8f4d905a18ebde4813f67c311fd9562298e885a253dc6c115: /usr/bin/kata-runtime did not terminate sucessfully: rpc error: code = Unknown desc = failed to write 0-4 to cpuset.cpus: write /sys/fs/cgroup/cpuset/docker/917b7fb254364fe8f4d905a18ebde4813f67c311fd9562298e885a253dc6c115/cpuset.cpus: invalid argument
: unknown
└─ $ docker update --cpus 4 foo
foo
└─ $ docker attach foo
root@917b7fb25436:/# nproc
1

also the communication with the container is closed, I found these messages in the journal

2018/05/30 19:28:22 [ERR] yamux: keepalive failed: i/o deadline reached
"agent grpc server quits" error="keepalive timeout"
"agent grpc channel teardown failed" error="close /dev/vport0p1: file already closed"

Expected result

5

Actual result

1

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions