This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add docker 4.0 blog post #2527
Add docker 4.0 blog post #2527
Changes from 9 commits
fe61423
a62d1f2
398e7d6
a18462f
eeb1cd9
ab0a89d
b3a03db
f029ea8
f8d621a
a45f1dd
b8de6a2
e4579c1
0e81fcd
7325226
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
i suggest adding the 50x figure in here to drive home the point early on
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.
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.
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.
i recommend downloading the GIF file and including it in Hugo so it can be embedded in here and not need to link off to a 3rd party site
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.
what is the significance of sentence 2 (schematizes all docker resources)? also, how come the Docker image resources could not participate in CRUD lifecycle before?
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.
The image resource is changing from a component to a custom type resource. The crux of many issues has been the limitations of the component type resource. The issue capturing this is referenced in the top of the article and here.
@gthuang Do you believe we need to go further in depth and explain why a component type resource is unable to participate in the CRUD lifecycle and is not schematized?
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.
@mnlumi i think it would be useful to at least mention that the image resource is now a custom resource (same as described in the original issue on this feature request), and that is why it can now participate in the CRUD lifecycle