Yusuke Kuoka

Results 885 comments of Yusuke Kuoka

Hey! Let me close this as already fixed via https://github.com/surrealdb/surrealdb.go/pull/209

Hey @erichorwath! > Execute following in a workflow or directly on the runner This is where I got confused- `dockerdContainerResources` sets the resources for the `docker` sidecar of the runner...

@erichorwath Thanks for your prompt reply! Could you also tell me how you exactly did this? > Execute following in a workflow or directly on the runner: `kubectl exec` commands...

@erichorwath Thanks a lot for the additional info! And yeah, your finding does make sense to me... Have you already tried our [dind-rootless-runners](https://github.com/actions/actions-runner-controller/blob/master/runner/actions-runner-dind-rootless.ubuntu-20.04.dockerfile)? Although it still require `privileged: true`, it...

@erichorwath In case dind-rootless runners turned out not to provide the resources-related isolation, we might still be able to recommend the usage of the [kuberenetes container mode](https://github.com/actions/actions-runner-controller/pull/1546) which uses K8s...

@erichorwath Thanks for the feedback! I'm quite confused now. I presume node crashes are issues in your K8s provider, not ARC, right? I understood that the K8s container mode would...

BTW... > leaving us with other strange side effects like non-removable runners from those effected nodes. If I'm not terribly confused, I think this is a standard [K8s behavior](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection) where...

@erichorwath Hey! I'm just saying ARC's kubernetes container mode does not depend on dind. The more you explain the issue, the more I think the k8s container mode would help.

@erichorwath Thanks again for your help! I'll definitely keep researching what we can do to support dind in cgroupv2 properly. > but Kind is for example not running on them....

Hi everyone! I was reviewing issues since 0.12.1 and found this one. Very detailed report! Much appreciated @rajesh-dhakad! AFAIK, the log `Waiting for runner container status to be available` should...