Eric Fang
Eric Fang
I am running into the same issue today, and am just introduced code with some extern "C". ``` extern "C" fn main(data: *mut libc::c_void) -> libc::c_int { unsafe { Box::from_raw(data...
Let me help and take a look
I can try to do some investigation around this and see if I can come up with a design. Work starts to take up more time, so I may work...
We should also differentiate short term and long term, perhaps? Limiting what we support in short term can allow us to focus on building new features. For long term, we...
Distros: Ubuntu/Debian and Fedora for near term. Likely we may want to support CentOS in the future, since it has a large server share as well. But CentOS usually carries...
> Also, we need to conditionally setup fields depending on which architecture we support: For example in State of container, pid is of data type i32, which is valid for...
In terms of kernel version, `libseccomp` will require us to have a newer kernel likely. Worst case, we disable `seccomp` for kernel version that doesn't support this? As mentioned before,...
Agree that we should increase the min kernel version supported in the future and we should not be afraid to do so. As far as architecture is concerned, I think...
> I think we probably already support arm64, but I don't really have a good setup to test that. If we didn't link against C libs it'd be easy to...
@tommady In general I am not a fan of github action or CI for performance benchmark. A local machine, ideally a physical box for this, should be preferred. There are...