Aleksa Sarai

Since `umoci`'s `oci/layer` library fixes this, this will be fixed when `oci/layer` moves here. And `umoci` already has tests to deal with this case.

This project is no longer actively maintained. However, [umoci] is a much more full-featured tool for manipulating OCI images, and is now an OCI project as a reference implementation of...

This project is no longer actively maintained. However, [umoci] is a much more full-featured tool for manipulating OCI images, and is now an OCI project as a reference implementation of...

A few questions I'd like to know the answer to (maybe even have mentioned in an RFC), is what CAP trade-off we should go for with multiple servers? Should be...

If you want to go this way @vishvananda (which I think would be awesome) I would recommend against going the `libcontainer` model. After talking to some people who wanted to...

Yup, but the `root.path` thing is more important than you might think on first reading. The `root.path` restrictions (and the whole "bundle" concept) make the API far more stateful than...

@aep The `root.path` issue is that there is a restriction in the OCI runtime-spec which states that `root.path` must be inside the "bundle" which contains the configuration file. Which means...

> Not sure if its intended, but railcar lets me specify a path outside the bundle for root, which will be on something like cafs for us. Heh, that's not...

@aep One of the maintainers has been [working on something like this][1], but there's still a lot of discussion that needs to happen in the spec (right now that design...

@crackcomm When referring to IPFS I was talking about the way the lazy fetching works, not the current implementation of IPFS. We don't plan to actually use IPFS for images...