-
Notifications
You must be signed in to change notification settings - Fork 885
Documentation: document image lifecycle and implementation. #2911
Conversation
--------------------- | ||
``` | ||
|
||
Currently rkt implements the appc spec, in future additional specs like (OCI) may be implemented keeping the same logic but chaning the implementations. |
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.
s/chaning/changing/
I've spotted some typos, but I guess @joshix may have additional inputs to reword some of these sentences. Great to have this information written down, the decoupling part at the bottom was not clear to me before. |
903dc9c
to
0e1c6ed
Compare
@lucab Thanks. Obviously there are better way to write the sentences 😄 The real intent is to explain how and why it works in this way, just to gather additional thoughts, better ideas and to have a starting point for future work on implementing the oci image spec. |
d0104fa
to
15ea291
Compare
@joshix ping :-) |
15ea291
to
0e2664d
Compare
ack, looking, sorry about the delay. Will review today. |
@joshix thanks, no problem. I was just going through milestoned PRs as tomorrow is release day. |
|
||
### Image lifecycle | ||
|
||
rkt commands like prepare and run, as a first step, needs to retrieve all the required images provided in the command line and prepare the stage2 directories with the application contents. |
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.
s/needs/need/
s/required images provided/images requested/
Document the image lifecycle phases, their logic and explain the rkt implementations.
0e2664d
to
864f661
Compare
LGTM |
Document the image lifecycle phases, their logic and explain the rkt implementations.