Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

oci support #226

Open
f0 opened this issue Dec 18, 2016 · 3 comments
Open

oci support #226

f0 opened this issue Dec 18, 2016 · 3 comments

Comments

@f0
Copy link
Contributor

f0 commented Dec 18, 2016

Hi,

any plans to implement oci support?

regards f0

@n0rad
Copy link
Member

n0rad commented Feb 3, 2017

I think rkt is still not ready to support OCI.
Also on our side ACI is working pretty well so it's not a big priority.
We will probably start working on it in 3-6 months.

@crackcomm
Copy link
Contributor

I was also interested in running OCI built with dgr mainly because of runc startup speed (can rkt be as fast?).
I found aci2oci converter but did not test it.

@n0rad
Copy link
Member

n0rad commented Feb 9, 2017

This is our plan too. rkt is flatting overlay and so is slow to start.
It's good for production, but not so much for dev iteration. Using aci2oci will not help since dgr is currently relying on rkt to build.

Now we are not sure yet if with runc, we will be able to meet the whole feature set of dgr.
Expecially since we are able to build in the stage1, using dependencies, and exporting the top layer of the overlay as result of the build.

This will require deep study to tell.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants