Control: severity -1 important On Thu, Nov 02, 2023 at 10:43:46AM -0500, Jesse Hathaway wrote: > Since this bug affects the current version in bookworm, v1.8.1, would > there be a possibility of adding the upstream patch to bookworm's > version? I tested applying the patches atop v1.8.1 and they apply > cleanly, and fix the issue as well. > > git checkout -b bookworm 1.8.1 > git cherry-pick 57262a2710c83fa08767f0ce3ba7a80993515bb2 > git cherry-pick 14afa8a46e2e83608a3a219402bce8ea8d071192
Despite Austin's description noting this, I had read the bug a bit in haste and thought this was only affecting crun 1.8.1 + Linux >= 6.6 (as crun's commit message mentioned). In other words, a combination of (crun from bookworm) + (Linux from sid), which, while not great, wasn't that big of an issue. However, after discussing this further with Jesse, I realized that the kernel commit in question (5d1f903f75a80daa4dfb3d84e114ec8ecbf29956, "attr: block mode changes of symlinks") has been backported as a stable upate to 6.1.55 (6a84939cc7dd6f970c2621ded82c4d9ea0068b1b), in turn part of src:linux 6.1.55-1, currently in bookworm. This means that bookworm's crun, combined with bookworm's current kernel, is broken when running containers with systemd as the init system. A simple test case is: podman run --rm -d docker.io/jrei/systemd-debian:12 I'm going to prepare a stable update backporting these two commits, hopefully resolving this incompatibility. Thanks all! Faidon
