Bug 1568570
Summary: | docker run --cpu-shares=N : fails: cgroup configuration: No such device or address | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ed Santiago <santiago> |
Component: | docker | Assignee: | Antonio Murdaca <amurdaca> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | adimania, admiller, amurdaca, david.sastre, dwalsh, fkluknav, ichavero, javilinux, jcajka, lsm5, marianne, nalin, santiago, shopper2k, vbatts |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-07 13:01:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ed Santiago
2018-04-17 19:14:01 UTC
Is this something that worked in previous versions? Or is this something that is broken using systemd cgroups versus cgroupfs? This is a standard docker-autotest subtest; it has been working AFAICT since docker-1.10 and possibly earlier. That makes the failure a regression. I get the same regression after upgrading docker to latest in Fedora 28 when attempting to start a container with '--cpu-shares' and '--memory' options. Server: Version: 1.13.1 API version: 1.26 (minimum version 1.12) Package version: docker-1.13.1-52.git89b0e65.fc28.x86_64 Go version: go1.10 Git commit: 70d5aac-unsupported Built: Fri Apr 13 05:49:55 2018 OS/Arch: linux/amd64 Experimental: false Error: /usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:258: applying cgroup configuration for process caused \"No such device or address\"". *** This bug has been marked as a duplicate of bug 1571736 *** |