Christophe de Dinechin

So I think that @lifupan's fix may actually address the "Link not found" case. I then have another failure, but the fix may be sufficient to address the `nerdctl` case.

Two duplicates with separate discussions and examples: #3765 and #10897. One proposal that would address it: #3976

@Joeknx Same observation here: reinstalling fixed the problem until I changed the output (switching to headset). After returning to the original audio output, it automatically shifts to the _[Name of...

The error seems to be emitted by [the agent here](https://github.com/kata-containers/kata-containers/blob/c2b06504916cb51f67f86a44011fcfee5cf36ad3/src/agent/src/netlink.rs#L295). This suggests that the veth pair is not correctly setup by CRIO before the agent actually launches. Is it possible...

The MAC address is different with every run, confirming that this is indeed a randomly-generated address. This seems to reinforce the idea that it might be a race.

Using `strace`, I believe that I was able to prove the timing issue. Running `strace` on `crio` as follows: ``` $ sudo strace -f -e trace=network,process,file -o /tmp/crio-trace.log -p $(pgrep...

Actually, there may be another problem. I tried comparing the MAC addresses generated by CNI and what the runtime is looking for. It's unclear to me that the MAC address...

Ran in a clean Fedora 42 VM installed using `kcli` and without installing `containerd` to avoid any interference. The exact same result was achieved. Here's a complete step-by-step summary to...

Ran on a fresh install of Fedora43, with a fresh Fedora 42 VM, and ran into the same problem. Some new things verified today: 1. Copying `cri-o/contrib/cni/11-crio-ipv4-bridge.conflist /etc/cni/net.d` from the...

I've tried detailed comparisons between 3 different configurations: 1. Fedora 2. RHCOS VM 3. OpenShift VM (running RHCOS as well) At the moment, I'm successful with the OpenShift VM, but...