Nadeshiko Manju

> Ideally we should wait for libseccomp v2.6 GA, but it doesn't seem planned soon. Yeah.... I will submit a issue to ask for the release plan

呜呜呜，我要举报你，来北京不和我面基（撒泼打滚号啕大哭（

This would be cool if we can config the binary path when running the container or via the config file. Would you mind to open a PR?

`Marshal.StringToCoTaskMemUTF8` would be more safety for this circumstance > [StringToCoTaskMemUTF8](https://learn.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.marshal.stringtocotaskmemutf8?view=net-7.0) is useful for custom marshaling or for use when mixing managed and unmanaged code. Because this method allocates the unmanaged...

> Maybe we should use `byte[]` in our .NET API instead of `string`? I don't think it's correct to use `UTF8` convert he I think the UTF8 here is enough...

> > I think the UTF8 here is enough for .NET binding. > > Can you elaborate more about this? We need to support writing data like png, pdf and...

> scheme in blocking_operator_construct: must be ascii like s3, memory. No other possible values. > path in blocking_operator_write: must be valid UTF-8 string. If we want to keep the same...

> content in blocking_operator_write: must be bytes. (I'm not sure how it represents in .NET) Agree,I will open other issue and take handle of it

> Okay, I understand: Even if it contains only ASCII characters, we still need to ensure that it's encoded in UTF-8. Yes, the encoding in windows world is always hard.

> @Xuanwo Hi, `oli` seems to be an awesome tool rocket I would like to get involved in the development! > > Before I can start, I would like to...