You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/Introduction.rst
+21-19Lines changed: 21 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,34 +36,35 @@ Sometimes we can find a publicly available container image for the exact workloa
36
36
37
37
Container Images aren’t actually images. They are repositories often made up of multiple layers. These layers can easily be added, saved, and shared with others by using a Containerfile (Dockerfile). This single file often contains all the instructions needed to build a new container image and can easily be shared with others publicly using tools like GitHub.
38
38
39
-
Here's an example of how to build a build a container image from content that resides in a git repository:
39
+
Here's an example of how to build a build a container image from content that resides in a git repository::
Building new images is great, but sharing our work with others lets them review our work, critique how we built them, and offer improved versions. Our newly built `hello` image can be published at quay.io or docker.io to share it with the world. Everything needed to run the `hello` application is provided in the container image. Others can easily pull it down and use it, or make improvements to it.
69
70
@@ -72,6 +73,7 @@ Standardizing on container images and `Container Registries`_ enable a new level
72
73
For example, if we wanted to share our newly built `hello` container image on quay.io it’s easy. First log in to quay::
0 commit comments