On Sun, Jan 18, 2026 at 01:43:11PM +0100, Bastian Blank wrote: > This invocation of crun is part of the cloud teams tooling, but not > in productive use yet. See > https://salsa.debian.org/cloud-team/debian-cloud-images/-/blob/master/src/debian_cloud_images/utils/sandbox.py?ref_type=heads
Thanks for the pointer! That's fascinating, always good to see new use cases :) > > Is this something that you just started to experience, or was this > > working in an older crun release? > > https://github.com/containers/crun/commit/405d2a2c5b851101a48025ddf6a79b2dddc8682f > > (part of 1.22) seems potentially relevant, so at minimum could you > > perhaps try with trixie's crun (1.21)? > > I'm pretty sure 1.24 worked. I just tried your config.json test case with 1.24-1, and got the same error. I then tried with 1.21, which resulted in: 2026-01-18T13:06:29.903261Z: executable file `/bin/false` not found: No such file or directory (which makes sense) I then ran a git bisect using good==1.21, bad==1.24, which identified the commit I guessed above (405d2a2) as the culprit. > > In any case, given you have a minimal reproduction case, and you seem to > > know what you're doing, perhaps this is something you'd like to report > > to upstream directly? In my experience they're fairly responsive. > > I'll try. Thanks! Faidon
