forked from docs/doc-exports
Dong, Qiu Jian
38e4c01e6c
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com> Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
27 lines
2.7 KiB
HTML
27 lines
2.7 KiB
HTML
<a name="swr_03_0003"></a><a name="swr_03_0003"></a>
|
|
|
|
<h1 class="topictitle1">Basic Concepts</h1>
|
|
<div id="body1513040558862"><div class="section" id="swr_03_0003__section32201017182910"><h4 class="sectiontitle">Image</h4><p id="swr_03_0003__p04131159182014">Images are like templates that include everything needed to run applications. When deploying containerized applications, you can use images from the Docker image center and your private image registries. For example, an image can contain a complete Ubuntu operating system, in which only the required programs and dependencies are installed. Docker images are used to create Docker containers. Docker provides an easy way to create and update your own images. You can also pull images created by other users.</p>
|
|
</div>
|
|
<div class="section" id="swr_03_0003__section10346312202412"><h4 class="sectiontitle">Container</h4><p id="swr_03_0003__p11284104718333">A container is a running instance of a Docker image. Multiple containers can run on one node. Containers are actually software processes. Unlike traditional software processes, containers have separate namespaces and do not run directly on a host.</p>
|
|
<p id="swr_03_0003__p145811426123720">Images become containers at runtime, that is, containers are created from images. Containers can be created, started, stopped, deleted, and suspended.</p>
|
|
</div>
|
|
<div class="section" id="swr_03_0003__section14458832965"><h4 class="sectiontitle">Repository</h4><p id="swr_03_0003__p180616351862">Image repositories are used for storing Docker images. An image repository hosts different versions of a specific containerized application.</p>
|
|
</div>
|
|
<div class="section" id="swr_03_0003__section33077262290"><h4 class="sectiontitle">Organization</h4><p id="swr_03_0003__p158371654133315">Organizations are used to isolate image repositories. With each organization being limited to one company or department, images can be managed in a centralized and efficient manner. A user can access different organizations as long as the user has corresponding permissions. Different permissions, namely read, write, and manage, can be assigned to different users in the same account.</p>
|
|
<div class="fignone" id="swr_03_0003__fig1924953913304"><span class="figcap"><b>Figure 1 </b>Organization</span><br><span><img id="swr_03_0003__image1225011398305" src="en-us_image_0195122694.png" height="393.01500000000004" width="523.6875" title="Click to enlarge" class="imgResize"></span></div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="swr_pd_index.html">Service Overview</a></div>
|
|
</div>
|
|
</div>
|
|
|
|
|
|
<script language="JavaScript">
|
|
<!--
|
|
image_size('.imgResize');
|
|
var msg_imageMax = "view original image";
|
|
var msg_imageClose = "close";
|
|
//--></script> |