Christophe de Dinechin

> On 7 Mar 2023, at 03:36, Toru Komatsu ***@***.***> wrote: > > > Not sure this is a good idea. Podman tries to figure out certain features of crun...

@utam0k Not an inconvenience at all. Thanks for pointing that out, I'll work on it.

I'm curious if there was any progress on that front since 2018? I started using Quaternion recently, and that's the most obvious missing feature.

That’s a good point. The recorder is intended for use in many programs. I will do that. Thanks Christophe > On 6 Dec 2017, at 21:20, Philippe Ombredanne wrote: >...

Actually, I need to double check. I created a script to maintain the headers in my projects. Right now, it spits out straight GPLv3, so I think that it may...

Hello Bastian, > On 18 Mar 2021, at 17:13, federkamm ***@***.***> wrote: > > > Hello Christophe, > > First, let me thank you very much for you very useful...

Hey @federkamm. Thanks a lot for your feedback. 1. You are right, will fix. 2. Interesting - I think I used what Fedora uses, but I may be wrong. I'll...

The problem might be related to having multiple "fedora" VMs at the same time. Setup of a Fedora 35 VMs, while I have a Rawhide microvm defined. ``` % krunvm...

The container indeed does not show up for `buildah`: ``` % buildah --root /Volumes/krunvm/root --runroot /Volumes/krunvm/runroot containers CONTAINER ID BUILDER IMAGE ID IMAGE NAME CONTAINER NAME 35038b6e9a92 * f8a1a9e13d62 registry.fedoraproject.org/fe......

Right after the first `create`, the container is there: ``` CONTAINER ID BUILDER IMAGE ID IMAGE NAME CONTAINER NAME 35038b6e9a92 * f8a1a9e13d62 registry.fedoraproject.org/fe... fedora-working-container c3e1d8d70c8c * 585393df054a docker.io/library/debian:latest debian-working-container e90f078efb2d...