Aleksa Sarai

@utam0k `process.start` doesn't actually start the process, that's actually the implementation of `runc create`. `runc start` calls `container.Exec`. (Yes this is confusing, this happened because when we added `runc create`...

I just merged the patchset which added support for that -- opencontainers/umoci#562. I have a few minor cleanup things to do then I'll do the release.

https://github.com/opencontainers/umoci/releases/tag/v0.5.0 has been released. There were some breaking API changes that you might need to update this PR to fix, but at a quick look it should Just Work As...

It would be quite helpful to know where in the kernel it is sleeping by looking at `/proc//stack`. You didn't mention what you were doing to trigger the issue --...

Yeah, removing bindfd fixed this (and we eventually switched to `fsopen("overlay")` by default for post-5.2 kernels in runc 1.2).

Yeah I saw the image-spec discussion. I suspect we will need to rework a few of the core CAS APIs to make it properly configurable...

There's also all of the mutate and main `umoci` APIs, which already have a lot of arguments so we really should rework how adding config arguments works... I'll add this...

@rchincha There are already breaking changes slated for `0.5`, but my current view is that we won't do a `/v2` API split for the following reasons: 1. umoci is still...

(This is also related to https://github.com/opencontainers/umoci/issues/323, btw.)

Just a note to myself -- this will need auto-selection logic, similar to our current compression auto-selection logic (though I think the most sane default would be to use the...