-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Singularity compliance with the OCI runtime #1235
Comments
Hiya @pimpim! I wholeheartedly agree! OCI compliance is a major part of our extended roadmap. |
Interested yes, but not practically able to attend! Maybe there is some sort of remote participation possible? |
+1 |
This document might be of interest, eg in the context of singularity registry https://docs.google.com/document/d/15y0SBrrDFIEM7pnU-Oe3Y6pq-eTZfo0mk-k33cS2hR4/edit#heading=h.kmkpd9i5mwli |
Hey @rdwrt sorry for the late response, we've been super busy getting the SyLabs org set up and churning. Onto the topic of OCI compliance, the issue has exclusively been we haven't had enough manpower to think about OCI. However now that SyLabs the company is set up, we have the resources to go forward with OCI. With Singularity 3.0 out on the horizon, we're rewriting our front end/CLI in Golang. Doing this will allow us to be much more flexible with supporting alternative runtime/image specifications, including OCI. This means that with version 3.0, Singularity will integrate directly and seamlessly into any tool that expects an OCI runtime. |
woohoo! hey @bauerm97 long time no see! You should be a part of the discussion here too: opencontainers/tob#35 and I have some (pretty silly) plans for continuing to learn Go, haha. :) |
It seems like this issue is pretty much finished now that 3.1 is out. I'll close. Feel free to ask if it needs to be re-opened. |
Great job guys! |
This is a regularly asked question, but I couldn't find a corresponding issue, maybe I searched incorrectly, but otherwise, here you go!
https://twitter.com/search?q=OCI%20singularity&src=typd
https://twitter.com/mr_openstack/status/887685486432714752
https://twitter.com/biocrusoe/status/947420025002086400
There doesn seem to be any technical reason not to do it, it mostly seems to be a time / human resource issue that prevents this from being implemented. Maybe this is a nice subject for any upcoming hackathon.
The text was updated successfully, but these errors were encountered: