Docker Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
Docker is at the same time a ''packaging format'', a ''set of tools'' with server and client components, and a ''development and operations workflow''. Because it defines a workflow, Docker can be seen as a tool that reduces the complexity of communication between the development and the operations teams. | Docker is at the same time a ''packaging format'', a ''set of tools'' with server and client components, and a ''development and operations workflow''. Because it defines a workflow, Docker can be seen as a tool that reduces the complexity of communication between the development and the operations teams. Docker architecture centers on atomic and throwaway [[#Container|containers]]. | ||
=Container= | |||
=Docker Workflow= | =Docker Workflow= | ||
Revision as of 19:12, 29 March 2017
Internal
Overview
Docker is at the same time a packaging format, a set of tools with server and client components, and a development and operations workflow. Because it defines a workflow, Docker can be seen as a tool that reduces the complexity of communication between the development and the operations teams. Docker architecture centers on atomic and throwaway containers.