Maksym Pavlenko
Maksym Pavlenko
Pushed https://github.com/containerd/containerd/pull/7061/commits/1eb20bf1d5a90b48e76fca7ea1375be606cec686 to omit reading from disk / unmarhsalling. We needed that just for `User` field, so its easy to workaround it with one more label instead.
ping @mikebrow @fuweid @dmcgowan is there anything else I can do here to push this forward?
> copying the windows/linux resource fields over here: https://github.com/containerd/containerd/pull/6517/files#diff-c2be5fd4b479b8b7191b7800ba25be98107c143e0a13575917220a4bfebe132aR101-R104 to eliminate the spec cost for the status checks... I've removed image spec reading in https://github.com/containerd/containerd/commit/1eb20bf1d5a90b48e76fca7ea1375be606cec686, this should reduce CPU pressure....
> In current containerd code implement, when a container task is created and started, the containerd would directly have a new ttrpc client to ttrpc sever of shimv2 so that,...
I think this partially intersects with https://github.com/containerd/ttrpc-rust/issues/132 `SOCK_CLOEXEC` fix applicable to both windows and mac os, so it make sense to use `not(linux)` or `any(windows, macos)`.
I don't have windows environment, so I haven't tried it. But it would be good to support all platforms though. I think a good starting point would be to get...
Sure, let's keep this open
I'm going to close this one. Please get back if you still experience this problem.
Will do!
@wllenyj are you doing any work for statuses? ^^^