-
I’d absolutely love to use nix-snapshotter with [podman]()'s [Quadlets]() for local, rootless `.container` and `.kube` systemd units. (I don’t know of an equivalent systemd generator for [k3s]().) Thi…
-
### Description
I have been tinkering to get runsc to work with crio and I think I have it mostly working. Except for the fact that initContainers don't seem to be supported properly.
Reading the …
-
### What happened?
in one node, when system load is high, and then we restart cri-o, the cri-o stuck in Restore process for a long time, the logs show as follows:
```
Oct 15 13:32:42 master-lharm-2…
-
Hey folks, I'm playing around with the idea of a generic CRI plugin interface for CRI-O based on WASM binaries: https://github.com/cri-o/cri-o/pull/8715
A pre-compiled WASM plugin can be used to modi…
-
```bash
$ docker exec -it container-checkpointing-control-plane /bin/bash
$ root@container-checkpointing-control-plane:/# crictl --runtime-endpoint unix:///run/crio/crio.sock pull registry.k8s.io/…
-
In https://github.com/inspektor-gadget/inspektor-gadget/actions/runs/7502984710/attempts/1#summary-20427218246 the TestTraceNetwork failed in cri-o, the most relevant part of the log is:
```
{"r…
-
### What happened?
Upgrade from CRI-O 1.30.6 to 1.30.7 causes error for kubelet and containers are not starting:
`"Container creation error: writing file devices.allow: Operation not permitted`
…
-
We are building an image-scanner K8s-operator, and all our clusters runs Openshift. Inspired by [trivy-operator](https://github.com/aquasecurity/trivy-operator), which we cannot use for various reason…
-
### What happened?
Hi,
I'm facing a problem with cri-o update.
Context : I manage a K8S cluster all the system is Debian 12. When I created the cluster I had used this repo (http://download.opens…
-
### What happened?
With the cri-o version(in 1.29), I see the default runtime is set to crun in /etc/crio/crio.conf.d/10-crio.conf
I had updated the cri-o version from 1.28.9 to 1.29.9 successfully …