{"version":"2.1.286","anchor":"cgroup-v1-path-parsing-fixed-for-paths-containing-colons","canonical_anchor":"cgroup-v1-path-parsing-fixed-for-paths-containing-colons","heading":"Container memory limits are read correctly when the path contains a colon","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/cgroup-v1-path-parsing-fixed-for-paths-containing-colons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Container memory limits are read correctly when the path contains a colon\n\nClaude Code no longer cuts short Linux cgroup paths that contain a colon, so it reads container memory limits correctly\n\n**Unclear.** It is not known which container setups produce cgroup paths with colons in them.\n\n**What**\n\nOn Linux, containers use a feature called cgroups (control groups) to set limits such as how much memory a program may use. Claude Code reads a system file to find which cgroup it runs in. Each line in that file has fields separated by colons.\n\nClaude Code used to keep only the third field, so a cgroup path that itself contained a colon was cut off at that colon. It now keeps the whole rest of the line, colons included.\n\n**Why**\n\nIn containers whose cgroup paths contain colons, Claude Code can now find the right memory limit instead of looking in the wrong place.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}