113xiaoji
113xiaoji
> > **Question 1**: At that time, what was consuming the memory? `memfd` shouldn't consume the container's memory. > > I have done some tests. Maybe depends on go's version....
I switched the Go version to 1.20.7, but the problem still persists. ```shell Warning FailedStart 7s kubelet Error: failed to create containerd task: failed to create shim: OCI runtime create...
> It should be noted that the cgroup configuration didn't fail when the process was first configured, so there's something weird going on here. It should also be noted that...
> I'm not sure if the cgroup configuration for `procHooks` is actually necessary -- we already set up the cgroups far earlier. IIRC the reason for this being added in...
> t should be noted that the cgroup configuration didn't fail when the process was first configured, so there's something weird going on here. It should also be noted that...
Do you need me to provide any additional information?
> Well, it is clear what's happening -- higher memory usage due to switching from bindfd to memfd. > > This is being addressed in #3987. If you want to...
OK i will reproduce later
> @113xiaoji #3987 has been merged, could you please test it to see whether you can reproduce your issue in the main branch or not. Thanks. I have tested it...
@kolyshkin After studying the source code, I found that when the cgroup is set to v2, the `Set` method no longer needs to freeze and thaw. However, even if I...