Tmp2: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
(Blanked the page)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
=tmp2=


=Docker and State Management=
==Environment Variables==
Containerized applications must avoid maintaining configuration in filesystem files - if they do, it limits the reusability of the container. A common pattern used to handle application configuration is to move configuration state into environment variables that can be passed to the application from the container. Docker supports environment variables natively, they are stored in the metadata that makes up a container configuration, and restarting the container will ensure the same configuration is passed to the application each time.
==Storing Files==
Storing state into the container's filesystem will not perform well. The space is extremely limited and the state will not be preserved across the container lifecycle.
==Application State==
The best use case for Docker is an application that can store state in a centralized location that could be accessed regardless of which host the container runs on.
=Image=
A ''container image'' is a ''read-only template'' consisting of one or more filesystem layers and metadata describing its needs and capabilities. Together they represent ''all'' the files required to run an application - the container image encapsulates all the dependencies of an application and configuration, and it can be deployed on any environment that has support for running containers. The same bundle can be assembled, tested and shipped to production without any change. Container images are a ''packaging technology''.
The image is produced by the [[docker build|build]] command, as the sole artifact of the build process. When an image needs to be rebuilt, every single layer after the first introduced change will need to be rebuilt. Each image has a [[#Tag|tag]].
Docker defines its own [[#Docker_Image_DSL|DSL]] (Domain Specific Language) for creating Docker images.
==Layer==
==Layered Image==
Each set of new changes made during the container build process is laid in top of previous changes. In general, each individual build step used to create the image corresponds to one filesystem layer. Each layer is identified by an unique long hexadecimal number named <span id='hash'></span>''hash''. The hash is usually shortened to 12 digits. If a shared image is updated, all containers that use it must be re-created.
The layers are [[#Docker_Revision_Control|version controlled]].

Latest revision as of 07:02, 5 December 2017

Retrieved from "https://kb.novaordis.com/index.php?title=Tmp2&oldid=33678"