Giuseppe Scrivano

I am fine doing it there, as it won't affect containers startup time

closing since #982 is merged

@chuanchang could you please rebase?

@chuanchang are you still working on this PR?

we would need to statically build and link wasmedge as well, and not use `dlopen` and `dlsym`.

I don't think it is a high priority issue that you should hurry to look at. Still it is not clear what are the advantages

yes, the main problem with the current headers is that they don't split correctly between what is public and what is used internally. How are you planning to use libcrun?...

if you would like, the bindings can be added to this git repo and be maintained here.

I've done some cleanup for the API: - api: unexport some functions #828 Getting to a usable header file will take some more time, now the public functions are just...

honestly, I am not sure about addressing it. There could be valid use cases for running different containers in the same cgroup, even if it is a weird configuration.