-
Notifications
You must be signed in to change notification settings - Fork 31
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
blog: Add "OCI Runtime Spec v1.1" #133
blog: Add "OCI Runtime Spec v1.1" #133
Conversation
cc @opencontainers/runtime-spec-maintainers @caniszczyk @amye |
f0f8d07
to
3212194
Compare
f24cf4f
to
404c2ce
Compare
@cyphar Thanks, applied your suggestions |
|
||
Note that the `CLOCK_REALTIME` clock (the best known Linux clock) is not isolated with time namespaces. | ||
|
||
runc doesn't implement time namespaces yet, but there is a [pull request](https://github.com/opencontainers/runc/pull/3876) to implement it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR completely slipped my mind. I'll work on getting this merged and we can update the blog post after it's merged. Not a blocker for publishing of course.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
In the past I think we usually wanted to get approval from @caniszczyk or @amye before posting something to the OCI website. There isn't an official maintainer list (since I worked on the site in the past, I have merge rights but I suspect I'm not supposed to use them?).
Co-authored-by: Aleksa Sarai <[email protected]> Signed-off-by: Akihiro Suda <[email protected]>
404c2ce
to
2707bd2
Compare
Changed the date to 2023-07-21 |
Looks like spec maintainers can just merge blog PRs by themselves now? |
Let me merge the spec v1.1 PR and this blog PR simultaneously.
(ETA: 2023-07-20)