Peter Hunt

the one linked: https://github.com/cri-o/cri-o/blob/main/internal/client/client.go

I would guess you could if you mounted in `/var/run/crio/crio.sock` and pointed crictl to it. There would likely be some selinux weirdness so the container probably has to be privileged...

sorry for the late reply--unfortunately not. accessing the cri-o socket needs to be a privileged operation, as direct access to the socket allows a user to do anything to the...

that sounds good! the impetus for opening this wasn't so much valid notes as it was succeeding in generating any notes. I don't have references now, but we semi-frequently hit...

you can chat on #crio in kubernetes slack or you can PM me @haircommander there as well :)

you can find them here https://github.com/cri-o/cri-o/actions?query=branch%3Av1.28.2 but we haven't had a failure like the one that prompted this in a while

would you mind turning on cri-o debugging logs, retrying, and getting us the logs? CRI-O logs a bunch more in debug for PullImage commands

[crio.zip](https://github.com/cri-o/cri-o/files/11140790/crio.zip) here I've trimmed some of the noise of debug logging. it does indeed seem like the request begins and disappears (begins on line 2953 of this file). We can...

similar to https://github.com/cri-o/cri-o/pull/4868, we would like more of the container and sandbox container creation to be moved to the respective factory package and unit tested. Ideally this would also involve...

yup that sounds good @hasan4791 . I would say a goal is to be able to remove the call to c.Spec() in server/container_create_linux.go and have all of the spec generation...