blog: Add "OCI Runtime Spec v1.1"#133
Conversation
|
cc @opencontainers/runtime-spec-maintainers @caniszczyk @amye |
AkihiroSuda
force-pushed
the
runtime-spec-v1.1.0
branch
2 times, most recently
from
f0f8d07 to
3212194
Compare
AkihiroSuda
force-pushed
the
runtime-spec-v1.1.0
branch
from
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.
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.
cyphar
left a comment
cyphar
left a comment
There was a problem hiding this comment.
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]>
AkihiroSuda
force-pushed
the
runtime-spec-v1.1.0
branch
from
404c2ce to
2707bd2
Compare
|
Changed the date to 2023-07-21 |
|
Looks like spec maintainers can just merge blog PRs by themselves now? |
5 participants
Let me merge the spec v1.1 PR and this blog PR simultaneously.
(ETA: 2023-07-20)