Vasiliy Ulyanov

> I cannot think of any reason why `RunAsGroup` is necessary, although it is strange that it will be `0` if not specified. It should be 1001 as well as...

I've finally managed to figure out what is going on. It's documented in the Kubernetes CRI API spec: > run_as_group should only be specified when run_as_user is specified; otherwise, the...

Ping @mhenriks, WDYT? Would it be okay to remove `RunAsGroup` from the pod spec? Seems that `cri-o` does not follow the API spec, and it does not error here. However,...

Ping @mhenriks, any objection about removing `RunAsGroup`? This should fix the exporting on the systems with `containerd`.

I had a similar issue. Fixed that using: ```yaml kubectl apply -f -

@brybacki , > CDI provides a collection of Storage Profiles with default recommended values for some **well known backends**. If the storage provisioner defined in storage class does not have...

I think the example yamls are meant to be used along with the test cluster which you can bring up with `make cluster-up`. This will also setup a local registry...

It looks like the init container fails. Could you provide the logs? ```bash kubectl logs -n kubevirt virt-handler-4w99d -c virt-launcher ``` Do you have apparmor running on your host?

> Permission denied I actually think you do have it. Check you system logs. Not sure where exactly you need to look in Debian. Perhaps `grep DEN /var/log/audit/audit.log` or `journalctl...

If its apparmor you can try to work around this issue with `aa-disable /usr/sbin/libvirtd`. But this is not a good solution for "production" as it will disable the security profile...