runc-update(8)

💅 runc-update — like, the manual page bestie 💅

okay so this is runc-update(8) from the System Manager's Manual and it's literally the glow-up button for your running containers. let's get into it 🫶

---

✨ 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 changes the resource constraints of a running container instance. not a new container, not a stopped one — a running one, bestie. mid-glow-up. 💖

You can set the resources with options, or, if -r is used, they get parsed from JSON that you hand over as a file or straight 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,
               "burst": 0,
               "period": 0,
               "realtimeRuntime": 0,
               "realtimePeriod": 0,
               "cpus": "",
               "mems": ""
          },
          "blockIO": {
               "blkioWeight": 0
          }
}

---

🎀 OPTIONS 🎀

• --resources|-r resources.json — reads the new resource limits from resources.json. use - to read from stdin. and listen: if this option is used, all other options are ignored. periodt. 🙈
• --blkio-weight weight — sets a new io weight.
• --cpu-period num — sets the CPU CFS period used for hardcapping (in microseconds).
• --cpu-quota num — sets the CPU usage limit within a given period (in microseconds).
• --cpu-burst num — sets the CPU burst limit within a given period (in microseconds).
• --cpu-rt-period num — sets the CPU realtime period used for hardcapping (in microseconds).
• --cpu-rt-runtime num — sets the CPU realtime hardcap limit (in usecs). that's the allowed cpu time in a given period, iykyk.
• --cpu-share num — sets CPU shares (relative weight vs. other containers).
• --cpuset-cpus list — sets the CPU(s) to use. the list can contain commas and ranges. for example: 0-3,7.
• --cpuset-mems list — sets the memory node(s) to use. same list format as --cpuset-cpus.
• --memory num — sets the memory limit to num bytes.
• --memory-reservation num — sets the memory reservation, aka the soft limit, to num bytes.
• --memory-swap num — sets total memory + swap usage to num bytes. use -1 to unset the limit (i.e. use unlimited swap). 🌀
• --pids-limit num — sets the maximum number of processes allowed in the container. use -1 to unset the limit.
• --l3-cache-schema value — sets the value for Intel RDT/CAT L3 cache schema.
• --mem-bw-schema value — sets the Intel RDT/MBA memory bandwidth schema.

---

👑 SEE ALSO 👑

runc(8).

---

okay that's the whole thing, no cap. this page lives in the System Manager's Manual and its name is runc-update(8) — slay, you're all caught up. go update something. 💅✨🦋