Skip to content

cannot remove memory constraints #22516

@anandkumarpatel

Description

@anandkumarpatel

docker update -m 0 <id> does not clear memory constraint

Output of docker version:

docker version
Client:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 21:37:01 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.2
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   c3959b1
 Built:        Mon Feb 22 21:37:01 2016
 OS/Arch:      linux/amd64

Output of docker info:

docker info
Containers: 8
 Running: 3
 Paused: 0
 Stopped: 5
Images: 23
Server Version: 1.10.2
Storage Driver: aufs
 Root Dir: /docker/aufs
 Backing Filesystem: extfs
 Dirs: 83
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.13.0-85-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.797 GiB
Name: ip-10-12-217-245.123
ID: 6D77:ZEEK:VXZN:PXJK:7GLA:TRAG:HN65:XD42:VPVP:SYKH:Q4IK:HZF7
WARNING: No swap limit support
Labels:
 org=123

Additional environment details (AWS, VirtualBox, physical, etc.):
AWS ubuntu instance

Steps to reproduce the issue:

docker create -m 1g busybox
dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20

docker inspect dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20 | grep "Memory"
            "Memory": 1073741824,

docker update -m 0 dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20
dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20

docker inspect dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20 | grep "Memory"
            "Memory": 1073741824,

docker update -m 4m dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20
dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20

docker inspect dba33cb016d80b25fc931383009f4f6a52deefd67fe23959763b7f792e4caf20 | grep "Memory"
            "CpusetMems": "",
            "KernelMemory": 0,
            "Memory": 4194304,

Describe the results you received:
Memory was not updated to 0

Describe the results you expected:
Memory was set to 0

Additional information you deem important (e.g. issue happens only occasionally):
100% repo rate

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.status/claimedversion/1.10

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions