)]}'
{
  "commit": "c21ef2315e06efe5ae2ad6d7b2bc92b68a726335",
  "tree": "9c6f9a48350714607e3eda8435a1af5c4a43c184",
  "parents": [
    "c164c4d9b90c35fdf950ac2f1d8323d53bb5df74"
  ],
  "author": {
    "name": "Kevin Berry",
    "email": "kpberry@google.com",
    "time": "Wed Apr 02 20:12:17 2025 +0000"
  },
  "committer": {
    "name": "Kevin Berry",
    "email": "kpberry@google.com",
    "time": "Wed Apr 02 20:25:48 2025 +0000"
  },
  "message": "toolbox: Force systemd-nspawn to use unified hierarchy\n\nBecause the toolbox image doesn\u0027t have systemd installed, systemd-nspawn\nassumes it must run in legacy cgroup v1 mode instead of in cgroup v2\nmode. This results in both cgroup v1 and v2 being used on an instance,\nregardless of the systemd.unified_cgroup_hierarchy setting. This default\nbehavior was fixed in\nhttps://github.com/systemd/systemd/commit/d89ee0fcf983ae765aab9629349225ca036482f1,\nbut applying that systemd patch could technically break users.\n\nAs a mitigation for existing COS milestones, we can set\nSYSTEMD_NSPAWN_UNIFIED_HIERARCHY\u003dyes for the systemd-nspawn call to\nforce toolbox to spawn with the unified v2 hierarchy, if possible. We\ncan defer applying the systemd patch to COS 125 and above.\n\nBUG\u003db/406594194,b/407615979\nTEST\u003dpresubmit, run modified toolbox script and ensure that it does not\nresult in hybrid cgroups, run modified toolbox on an instance using\nhybrid cgroups and ensure that it doesn\u0027t error\nRELEASE_NOTE\u003dModified toolbox to use unified cgroup hierarchy mode instead of hybrid mode when possible.\n\nChange-Id: Ic4834396055cbea6fcfb8d464c089db4adc4d243\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "787ce9d7e5197eea77e718c2bc06680faf21a71d",
      "old_mode": 33261,
      "old_path": "toolbox",
      "new_id": "61c4061bbea933c3d10a90c4ead39ce29516ef5e",
      "new_mode": 33261,
      "new_path": "toolbox"
    }
  ]
}