Scroll to navigation

runc-update(8) System Manager's Manual runc-update(8)

NAME

runc-update - update running container resource constraints

SYNOPSIS

runc update [option ...] container-id

runc update -r resources.json|- container-id

DESCRIPTION

The update command change the resource constraints of a running container instance.

The resources can be set using options, or, if -r is used, parsed from JSON provided as a file or from stdin.

In case -r is used, the JSON format is like this:

{
	"memory": {
		"limit": 0,
			"reservation": 0,
			"swap": 0,
			"kernel": 0,
			"kernelTCP": 0
	},
		"cpu": {
			"shares": 0,
			"quota": 0,
			"period": 0,
			"realtimeRuntime": 0,
			"realtimePeriod": 0,
			"cpus": "",
			"mems": ""
		},
		"blockIO": {
			"blkioWeight": 0
		}
}

OPTIONS

Read the new resource limits from resources.json. Use - to read from stdin. If this option is used, all other options are ignored.

Set a new io weight.

Set CPU CFS period to be used for hardcapping (in microseconds)

Set CPU usage limit within a given period (in microseconds).

Set CPU realtime period to be used for hardcapping (in microseconds).

Set CPU realtime hardcap limit (in usecs). Allowed cpu time in a given period.

Set CPU shares (relative weight vs. other containers).

Set CPU(s) to use. The list can contain commas and ranges. For example: 0-3,7.

Set memory node(s) to use. The list format is the same as for --cpuset-cpus.

Set memory limit to num bytes.

Set memory reservation, or soft limit, to num bytes.

Set total memory + swap usage to num bytes. Use -1 to unset the limit (i.e. use unlimited swap).

Set the maximum number of processes allowed in the container.

Set the value for Intel RDT/CAT L3 cache schema.

Set the Intel RDT/MBA memory bandwidth schema.

SEE ALSO

runc(8).